JDK-8214576 : 5 jck vm/constantpool/Initialization/Initialization010 fails in Graal as JIT mode with -Xcomp and AOTed Graal
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 12
  • Priority: P3
  • Status: Closed
  • Resolution: Duplicate
  • Submitted: 2018-12-01
  • Updated: 2018-12-13
  • Resolved: 2018-12-13
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 12
12Resolved
Related Reports
Duplicate :  
JDK-8214023 - Update Graal
Description
Following jck vm/constantpool/Initialization/Initialization010 tests fails when running in Graal as JIT mode with -Xcomp and AOTed Graal:

vm/constantpool/Initialization/Initialization010/Initialization01001m016
vm/constantpool/Initialization/Initialization010/Initialization01001m017
vm/constantpool/Initialization/Initialization010/Initialization01001m019
vm/constantpool/Initialization/Initialization010/Initialization01001m018
vm/constantpool/Initialization/Initialization010/Initialization01001m020

The issue is not seen without -Xcomp or without Graal.
Comments
lang/INTF/intf049/intf04901 still fails. Perhaps it is different issue, I will file new bug.
12-12-2018
Looks like it fixed the issue. Previously failed vm/constantpool/Initialization/Initialization010 tests do pass now.
12-12-2018
[~epavlova] Can you check if this is fixed now?
12-12-2018
A classic 1 missing character error: diff --git a/compiler/src/org.graalvm.compiler.java/src/org/graalvm/compiler/java/BytecodeParser.java b/compiler/src/org.graalvm.compiler.java/src/org/graalvm/compiler/java/BytecodeParser.java index 1147a9cc776..fa43b89f2f9 100644 --- a/compiler/src/org.graalvm.compiler.java/src/org/graalvm/compiler/java/BytecodeParser.java +++ b/compiler/src/org.graalvm.compiler.java/src/org/graalvm/compiler/java/BytecodeParser.java @@ -1447,7 +1447,7 @@ public class BytecodeParser implements GraphBuilderContext { if (callTargetIsResolved(target)) { ResolvedJavaMethod resolvedTarget = (ResolvedJavaMethod) target; ResolvedJavaType holder = resolvedTarget.getDeclaringClass(); - if (!holder.isInitialized() && ResolveClassBeforeStaticInvoke.getValue(options)) { + if (!holder.isInitialized() && !ResolveClassBeforeStaticInvoke.getValue(options)) { handleUnresolvedInvoke(target, InvokeKind.Static); } else { ValueNode classInit = null;
03-12-2018
Can we run at least one test with normal Graal JIT (not AOTed) regardless how long it would take?
03-12-2018
We need to find if it is AOT or Graal issue.
03-12-2018
[~dnsimon] We use AOTed Graal so that we can run with -Xcomp to compile the test methods by Graal. You can try libgraal.so instead of AOTed. [~epavlova] Can you show final command line for case when C2 is used instead of AOTed graal? Can we reused directories and file after after your 'make run-test ' command to do that?
03-12-2018