RFR: 8309136: [JVMCI] add -XX:+UseGraalJIT flag [v2]

[David Holmes]

On Wed, 31 May 2023 08:08:34 GMT, Doug Simon <dnsimon at openjdk.org> wrote:

>> Use of the Graal-based JIT in OpenJDK currently requires the following flag: `-XX:+EnableJVMCIProduct`
>> 
>> This has no direct association with Graal. If the JDK image happens to include a non-Graal JVMCI implementation, it will be automatically selected. This would come as a surprise to users who equate JVMCI with Graal.
>> 
>> This PR introduces a new flag, `-XX:+UseGraalJIT` to address these shortcomings. The VM fails fast at startup if there is a non-Graal JVMCI implementation or no JVMCI implementation in the JDK image.
>
> Doug Simon has updated the pull request incrementally with one additional commit since the last revision:
> 
>   review based fixes

In the CSR request when asked about the response when the run-time image does not include the Graal JIT you pointed to this Java code:
https://github.com/openjdk/jdk/blob/927a9ed68371597eba1609f97ac03dd1de812e26/src/jdk.internal.vm.ci/share/classes/jdk/vm/ci/hotspot/HotSpotJVMCICompilerConfig.java#L112
but it seems to me that the logic in arguments.cpp handles the case where Graal is not available. Or are there different levels of "availability" here?

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

PR Comment: https://git.openjdk.org/jdk/pull/14231#issuecomment-1569717552