compiler/jvmci/compilerToVM/HasCompiledCodeForOSRTest.java fails with Graal
Christian Thalinger
cthalinger at twitter.com
Mon Jun 26 23:37:15 UTC 2017
So, this change:
$ hg log -r fbb9c8026495 -p compiler/jvmci/compilerToVM/HasCompiledCodeForOSRTest.java
changeset: 12748:fbb9c8026495
tag: jdk-9+168
user: dnsimon
date: Fri Apr 28 02:54:05 2017 -0700
summary: 8177845: Need a mechanism to load Graal
diff --git a/test/compiler/jvmci/compilerToVM/HasCompiledCodeForOSRTest.java b/test/compiler/jvmci/compilerToVM/HasCompiledCodeForOSRTest.java
--- a/test/compiler/jvmci/compilerToVM/HasCompiledCodeForOSRTest.java
+++ b/test/compiler/jvmci/compilerToVM/HasCompiledCodeForOSRTest.java
@@ -39,7 +39,7 @@
* @run main/othervm -Xbootclasspath/a:.
* -XX:+UnlockDiagnosticVMOptions -XX:+WhiteBoxAPI
* -XX:+UnlockExperimentalVMOptions -XX:+EnableJVMCI
- * -XX:-BackgroundCompilation
+ * -XX:-BackgroundCompilation -Djvmci.Compiler=null
* compiler.jvmci.compilerToVM.HasCompiledCodeForOSRTest
*/
sets the JVMCI compiler to null. How is this test supposed to work when running with UseJVMCICompiler and Graal?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openjdk.java.net/pipermail/hotspot-compiler-dev/attachments/20170626/87b3a522/attachment-0001.html>
More information about the hotspot-compiler-dev
mailing list