-
Bug
-
Resolution: Fixed
-
P3
-
11, 12
-
b08
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8291815 | 11.0.18-oracle | Kavya K S | P3 | Resolved | Fixed | b01 |
I noticed that some tests are run in our Graal nightlies although the @requires explicitly states:
!vm.graal.enabled
for example:
test/hotspot/jtreg/compiler/intrinsics/bmi/verifycode/AndnTestI.java
Turns out the code in Compiler.isGraalEnabled still checks for:
// This check might be redundant but let's keep it for now.
String jvmciCompiler = System.getProperty("jvmci.Compiler");
if (jvmciCompiler == null || !jvmciCompiler.equals("graal")) {
return false;
}
but this property is not set and is null by default.
!vm.graal.enabled
for example:
test/hotspot/jtreg/compiler/intrinsics/bmi/verifycode/AndnTestI.java
Turns out the code in Compiler.isGraalEnabled still checks for:
// This check might be redundant but let's keep it for now.
String jvmciCompiler = System.getProperty("jvmci.Compiler");
if (jvmciCompiler == null || !jvmciCompiler.equals("graal")) {
return false;
}
but this property is not set and is null by default.
- backported by
-
JDK-8291815 Compiler.isGraalEnabled should not check jvmci.Compiler property
-
- Resolved
-
- duplicates
-
JDK-8263251 fix initialization of vm.graal.enabled
-
- Closed
-