-
Bug
-
Resolution: Fixed
-
P4
-
11-pool, 17-pool, 18
-
b25
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8279193 | 17.0.3-oracle | Vladimir Kozlov | P4 | Resolved | Fixed | b01 |
JDK-8279226 | 17.0.3 | Vladimir Kozlov | P4 | Resolved | Fixed | b01 |
JDK-8278861 | 11.0.15-oracle | Vladimir Kozlov | P4 | Resolved | Fixed | b01 |
JDK-8279178 | 11.0.15 | Vladimir Kozlov | P4 | Resolved | Fixed | b01 |
# Internal Error (nativeInst_x86.cpp:155), pid=19, tid=0x00007f410b0f4700
# guarantee(!os::is_MP() || is_aligned) failed: destination must be aligned
This implies a problem in Graal in terms of emitting code that complies with HotSpot's code patching requirements. It would be preferable for the compilation to fail gracefully/silently than for the whole VM to stop. As such, JVMCI should verify these alignment invariants during code installation.
- backported by
-
JDK-8278861 [JVMCI] check alignment of call displacement during code installation
- Resolved
-
JDK-8279178 [JVMCI] check alignment of call displacement during code installation
- Resolved
-
JDK-8279193 [JVMCI] check alignment of call displacement during code installation
- Resolved
-
JDK-8279226 [JVMCI] check alignment of call displacement during code installation
- Resolved
- relates to
-
JDK-8283306 re-resolving indirect call to non-entrant nmethod can crash
- Resolved
-
JDK-8278747 [JVMCI] check alignment of call displacement during code installation
- Closed
- links to
-
Commit openjdk/jdk11u-dev/89898237
-
Commit openjdk/jdk17u-dev/81cd5940
-
Commit openjdk/jdk/2f4b5405
-
Review openjdk/jdk11u-dev/723
-
Review openjdk/jdk17u-dev/33
-
Review openjdk/jdk/6218