Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8270307

C2: assert(false) failed: bad AD file after JDK-8267687

    XMLWordPrintable

Details

    • b32
    • Verified

    Backports

      Description

        Bisection shows that the attached Fuzzer test starts to fail after JDK-8267687. Note it reproduces even with JDK-8268883 that is both in JDK 17 and already merged to JDK 18 master.

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

        Default case invoked for:
           opcode = 114, "Con"
        o1 Con === o0 [[]] #top

        --N: o1 Con === o0 [[]] #top

        # To suppress the following error report, specify this argument
        # after -XX: or in .hotspotrc: SuppressErrorAt=/matcher.cpp:1681
        #
        # A fatal error has been detected by the Java Runtime Environment:
        #
        # Internal Error (/home/shade/trunks/jdk/src/hotspot/share/opto/matcher.cpp:1681), pid=999395, tid=999408
        # assert(false) failed: bad AD file

        Attachments

          1. 0006.zip
            10 kB
          2. hs_err_pid1006718.log
            112 kB
          3. replay_pid1006718.log
            111 kB

          Issue Links

            backported by

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8270999 C2: assert(false) failed: bad AD file after JDK-8267687

            • P2 - Crashes, loss of data, severe memory leak.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8271629 C2: assert(false) failed: bad AD file after JDK-8267687

            • P2 - Crashes, loss of data, severe memory leak.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8271751 C2: assert(false) failed: bad AD file after JDK-8267687

            • P2 - Crashes, loss of data, severe memory leak.
            • Resolved
            relates to

            Enhancement - null JDK-8252372 Check if cloning is required to move loads out of loops in PhaseIdealLoop::split_if_with_blocks_post()

            • P3 - Major loss of function.
            • Resolved

            Enhancement - null JDK-8267687 ModXNode::Ideal optimization is better than Parse::do_irem

            • P4 - Minor loss of function, or other problem where easy workaround is present.
            • Resolved
            links to

            Commit Commit openjdk/jdk17/0cec11d3

            Review Review openjdk/jdk17/254

            Review Review openjdk/jdk/4796

            Activity

              People

                yyang Yi Yang
                shade Aleksey Shipilev
                Votes:
                0 Vote for this issue
                Watchers:
                8 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved: