| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8321583 | 8u411 | Daniel Skantz | P2 | Closed | Fixed | b01 |
[~never] pointed out that a fix for an assert on x86 that came in via JDK-8062493:
http://hg.openjdk.java.net/jdk9/hs-comp/hotspot/diff/a41fe5ffa839/src/cpu/x86/vm/compiledIC_x86.cpp#l1.34
should also be done on all other architectures. The failure manifests as:
# assert(method_loader->data() == 0 || method_loader->data() == (intptr_t)callee()) failed: a) MT-unsafe modification of inline cache
It depends on whether in an optimized debug build it managed to fold those reads into one.
http://hg.openjdk.java.net/jdk9/hs-comp/hotspot/diff/a41fe5ffa839/src/cpu/x86/vm/compiledIC_x86.cpp#l1.34
should also be done on all other architectures. The failure manifests as:
# assert(method_loader->data() == 0 || method_loader->data() == (intptr_t)callee()) failed: a) MT-unsafe modification of inline cache
It depends on whether in an optimized debug build it managed to fold those reads into one.
- backported by
-
JDK-8321583 fix assert in CompiledStaticCall::set_to_interpreted
-
- Closed
-
- relates to
-
JDK-8067247 Crash: assert(method_holder->data() == 0 ...) failed: a) MT-unsafe modification of inline cache
-
- Resolved
-
-
JDK-8062493 JEP 243: Java-Level JVM Compiler Interface
-
- Closed
-