RFR(S) 8186144: [Graal] some tests fail with: Improperly specified VM option UseJVMCICompiler: EnableJVMCI cannot be disabled
cthalinger at twitter.com
Fri Aug 25 22:52:06 UTC 2017
> On Aug 25, 2017, at 12:41 PM, Vladimir Kozlov <vladimir.kozlov at oracle.com> wrote:
> On 8/25/17 3:39 PM, Christian Thalinger wrote:
>>> On Aug 25, 2017, at 12:33 PM, Vladimir Kozlov <vladimir.kozlov at oracle.com> wrote:
>>> webrev: http://cr.openjdk.java.net/~kvn/8186144/webrev/
>>> Some jvmci tests disable JVMCI which cause problems if Graal is used as JIT. In such cases disable Graal by switching off UseJVMCICompiler.
>> Is it always guaranteed that the flags in the @run directive win over the ones passed on the command line?
Thanks for confirming. I wasn’t sure. Looks good.
>>> I also removed OSR compilation request from DisassembleCodeBlobTest.java because Graal correctly complains that compiled methods don't have loop.
>>> In SecurityRestrictionsTest.java I disable Graal in NO_JVMCI_ACCESS_PERM case when access restriction is enforced on JVMCI - we can't start Graal in such case.
>>> RBT and local testing.
More information about the hotspot-compiler-dev