JDK-8316868 : assert(!n->is_Phi() || n->as_Phi()->inst_mem_id() == -1) failed: should not be linked to data Phi
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 8,11
  • Priority: P4
  • Status: Closed
  • Resolution: Duplicate
  • OS: generic
  • CPU: generic
  • Submitted: 2023-09-21
  • Updated: 2023-09-25
  • Resolved: 2023-09-25
Related Reports
Duplicate :  
Description
ADDITIONAL SYSTEM INFORMATION :
# JRE version: OpenJDK Runtime Environment (8.0_392) (build 1.8.0_392-internal-fastdebug-b00)
# Java VM: OpenJDK 64-Bit Server VM (25.392-b00-fastdebug compiled mode linux-amd64 compressed oops)

A DESCRIPTION OF THE PROBLEM :
I ran a modified testcase using JDK8u392 and I found the JVM crashed under the option  -Xcomp  -XX:+UnlockExperimentalVMOptions  -XX:+AggressiveUnboxing

# A fatal error has been detected by the Java Runtime Environment:
#
#  Internal Error (/data/jdk8u/hotspot/src/share/vm/opto/phaseX.cpp:471), pid=20619, tid=0x00007f1ffa050700
#  assert(!n->is_Phi() || n->as_Phi()->inst_mem_id() == -1) failed: should not be linked to data Phi
#
# JRE version: OpenJDK Runtime Environment (8.0_392) (build 1.8.0_392-internal-fastdebug-b00)
# Java VM: OpenJDK 64-Bit Server VM (25.392-b00-fastdebug compiled mode linux-amd64 compressed oops)
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.java.com/bugreport/crash.jsp

STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
java  -Xcomp  -XX:+UnlockExperimentalVMOptions  -XX:+AggressiveUnboxing  TestDoubleBoxing

EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
Passed
ACTUAL -
# To suppress the following error report, specify this argument
# after -XX: or in .hotspotrc:  SuppressErrorAt=/phaseX.cpp:471
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  Internal Error (/data/jdk8u/hotspot/src/share/vm/opto/phaseX.cpp:471), pid=17724, tid=0x00007f636a959700
#  assert(!n->is_Phi() || n->as_Phi()->inst_mem_id() == -1) failed: should not be linked to data Phi
#
# JRE version: OpenJDK Runtime Environment (8.0_392) (build 1.8.0_392-internal-fastdebug-b00)
# Java VM: OpenJDK 64-Bit Server VM (25.392-b00-fastdebug compiled mode linux-amd64 compressed oops)
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /home/repository/bugs/TestDoubleBoxing_09_21_14_55_28/hs_err_pid17724.log
#
# Compiler replay data is saved as:
# /home/repository/bugs/TestDoubleBoxing_09_21_14_55_28/replay_pid17724.log
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.java.com/bugreport/crash.jsp
#
Current thread is 140064966678272
Dumping core ...


---------- BEGIN SOURCE ----------

---------- END SOURCE ----------

FREQUENCY : always



Comments
Duplicate of JDK-8217918.
25-09-2023

Issue is reproduced. Crash is observed on JDK 8 and JDK 11 fastdebug build. OS: Windows 10 JDK 8u381 Fastdebug: Fail JDK 11.0.20 Fastdebug : Fail JDK 17.0.8: Pass JDK 21: Pass ILW = Crash, reproducible on debug build, no known workaround yet = MLM = P4 Moving it to dev team for further analysis.
25-09-2023