JDK-8218927 : [libgraal] assert(failure_reason != 0LL) failed: must specify failure_reason
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: repo-metropolis
  • Priority: P3
  • Status: Closed
  • Resolution: Duplicate
  • OS: generic
  • CPU: generic
  • Submitted: 2019-02-13
  • Updated: 2024-06-10
  • Resolved: 2019-03-19
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.
Other
repo-metropolisResolved
Related Reports
Duplicate :  
JDK-8219995 - Update JVMCI
Relates :  
JDK-8218847 - [libgraal] port JVMCI support for libgraal
Description
During testing of JDK-8218847 changes I found few failures. This is one of them:

With " -XX:+UnlockExperimentalVMOptions -XX:+EnableJVMCI -XX:+TieredCompilation -XX:+UseJVMCICompiler -Djvmci.Compiler=graal" flags
test/hotspot/jtreg/compiler/uncommontrap/DeoptReallocFailure.java hit assert:

# Internal Error (src/hotspot/share/compiler/compileBroker.cpp:2084), pid=41624, tid=47068 
# assert(failure_reason != 0LL) failed: must specify failure_reason
Comments
GR-14278 fix was included in JDK-8219995 changes.
19-03-2019
I'll take care of backporting the two I provided fixes for.
01-03-2019
[~never] Do you want me to file jvmci-8 PR for this or you will do that?
01-03-2019
The get_jvmci_method call needs to handle exceptions as well. The attached fix2.patch handles this.
15-02-2019