-
Bug
-
Resolution: Fixed
-
P4
-
21, 23, 24
-
b17
-
generic
-
generic
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8342209 | 23.0.2 | Paul Hohensee | P4 | Resolved | Fixed | master |
Disabling the JVMCI compiler with `-XX:-UseJVMCICompiler` not only deactivates JVMCI-based CompileBroker compilations but also prevents the loading of the libjvmci compiler. While this works as expected for CompileBroker compilations, it poses issues for the Truffle compiler. When `-XX:-UseJVMCICompiler` is used, Truffle falls back to the jargraal compiler, if available. This behavior may be confusing for Truffle users.
Expected behavior:
With `-XX:+UseGraalJIT`, both CompileBroker compilations and Truffle compilations should utilize the libjvmci compiler, if available.
With `-XX:+EnableJVMCI`, CompileBroker compilations should use the C2 compiler, while only Truffle compilations should leverage the libjvmci compiler, if available.
Expected behavior:
With `-XX:+UseGraalJIT`, both CompileBroker compilations and Truffle compilations should utilize the libjvmci compiler, if available.
With `-XX:+EnableJVMCI`, CompileBroker compilations should use the C2 compiler, while only Truffle compilations should leverage the libjvmci compiler, if available.
- backported by
-
JDK-8342209 [JVMCI] Unintuitive behavior of UseJVMCICompiler option
- Resolved
- relates to
-
JDK-8340576 Some JVMCI flags are inconsistent
- Resolved
- links to
-
Commit(master) openjdk/jdk23u/c326ff12
-
Commit(master) openjdk/jdk/4cd8c75a
-
Review(master) openjdk/jdk21u-dev/1024
-
Review(master) openjdk/jdk23u/136
-
Review(master) openjdk/jdk/21069
(2 links to)