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 have equated JVMCI with Graal.
To address this, I propose to introduce a new flag, -XX:+UseGraalJIT, such that the Graal JIT can be enabled with:
-XX:+UseGraalJIT
The VM will then fail at startup if there is a non-Graal JVMCI implementation or no JVMCI implementation in the JDK image.
-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 have equated JVMCI with Graal.
To address this, I propose to introduce a new flag, -XX:+UseGraalJIT, such that the Graal JIT can be enabled with:
-XX:+UseGraalJIT
The VM will then fail at startup if there is a non-Graal JVMCI implementation or no JVMCI implementation in the JDK image.
- csr for
-
JDK-8309137 [JVMCI] add -XX:+UseGraalJIT flag
-
- Closed
-
- duplicates
-
JDK-8309199 [JVMCI] assert(is_jvmci_compiler() && is_jvmci() || !is_jvmci_compiler()) failed: JVMCI compiler implies enabled JVMCI
-
- Closed
-
- relates to
-
-
- Resolved
-
