RFR: 8340398: [JVMCI] Unintuitive behavior of UseJVMCICompiler option [v3]

[duke]

On Tue, 24 Sep 2024 07:15:57 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.
>
> Tomáš Zezula has updated the pull request incrementally with one additional commit since the last revision:
> 
>   JDK-8340398: Fixed UseJVMCINativeLibrary doc string.

@tzezula 
Your change (at version 28dbd9329a4ad67a39e3ba19767aea2209313382) is now ready to be sponsored by a Committer.

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

PR Comment: https://git.openjdk.org/jdk/pull/21069#issuecomment-2370858957