-
Bug
-
Resolution: Fixed
-
P5
-
24
-
b18
The interaction of some JVMCI flags is suboptimal. For example, the help for UseJVMCINativeLibrary says it defaults to true if EnableJVMCIProduct is true but EnableJVMCIProduct is a macro flag and the implementation actually checks UseJVMCICompiler. There are also a number of places in the code guarded by UseJVMCICompiler that should instead be guarded by EnableJVMCI. JDK-8340398 is fixing one such instance of this but there's almost certainly other places that needed to be fixed up.
As background, the motiviating use case of `-XX:+EnableJVMCI -XX:-UseJVMCICompiler` is Truffle when the user wants to use C2 for CompilerBroker JIT compilations but still use Graal for Truffle partial-evaluation compilations.
As background, the motiviating use case of `-XX:+EnableJVMCI -XX:-UseJVMCICompiler` is Truffle when the user wants to use C2 for CompilerBroker JIT compilations but still use Graal for Truffle partial-evaluation compilations.
- relates to
-
JDK-8340974 Ambiguous name of jtreg property vm.libgraal.enabled
-
- Resolved
-
-
JDK-8340398 [JVMCI] Unintuitive behavior of UseJVMCICompiler option
-
- Resolved
-
- links to
-
Commit(master) openjdk/jdk/5d062e24
-
Review(master) openjdk/jdk/21120