JDK-8270296 : C2: Another assert(!had_error) failed: bad dominance
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 17,18
  • Priority: P2
  • Status: Closed
  • Resolution: Duplicate
  • Submitted: 2021-07-12
  • Updated: 2021-07-13
  • Resolved: 2021-07-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 17
17Resolved
Related Reports
Duplicate :  
JDK-8269752 - C2: assert(false) failed: Bad graph detected in build_loop_late
Relates :  
JDK-8252372 - Check if cloning is required to move loads out of loops in PhaseIdealLoop::split_if_with_blocks_post()
Description
Not sure if that is something already fixed by already open issues, but I am putting it here for completeness. 
Bisection points to JDK-8252372 yet again. Reproduces on latest master:

$ git describe master
jdk-18+5-77-gac75a53fc51

Unpack the attached fuzzer test and run:

$ ../build/linux-x86_64-server-fastdebug/images/jdk/bin/java -Xmx512m -Xcomp -XX:CompileOnly=Test Test

#  Internal Error (/home/shade/trunks/jdk/src/hotspot/share/opto/loopnode.cpp:4931), pid=225012, tid=225025
#  assert(!had_error) failed: bad dominance
Comments
ILW = C2 assertion failure (recent regression in JDK 17 b24), only fails with single Java Fuzzer test, disable compilation of affected method = HMM = P2 This reproduces with latest JDK 17/18 which means it is either a newly detected issue or a dup of JDK-8269752. Can you have a look at it [~roland]?
12-07-2021