Integrated: 8340398: [JVMCI] Unintuitive behavior of UseJVMCICompiler option

Tomáš Zezula duke at openjdk.org
Tue Sep 24 10:22:43 UTC 2024


On Wed, 18 Sep 2024 16:53:40 GMT, Tomáš Zezula <duke at openjdk.org> wrote:

> 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.

This pull request has now been integrated.

Changeset: 4cd8c75a
Author:    Tomas Zezula <tzezula at openjdk.org>
Committer: Doug Simon <dnsimon at openjdk.org>
URL:       https://git.openjdk.org/jdk/commit/4cd8c75a55163be33917b1fba9f360ea816f3aa9
Stats:     21 lines in 3 files changed: 12 ins; 3 del; 6 mod

8340398: [JVMCI] Unintuitive behavior of UseJVMCICompiler option

Reviewed-by: dnsimon

-------------

PR: https://git.openjdk.org/jdk/pull/21069


More information about the hotspot-compiler-dev mailing list