G1: Incorrect code generated for G1 pre-barrier by C1 on SPARC

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: P3
    • hs17
    • Affects Version/s: 6u19
    • Component/s: hotspot
    • gc
    • b03
    • sparc
    • solaris_10

        While investigating a G1 issue with a customer supplied test case I tried running the test case with a 32 bit client JVM on our batoka machine. The original issue is a possible race with concurrent marking so I ran the test case with ParallelMarkingThreads=1.

        After around 4 hours the test case failed with an assert that the contents of an SATB buffer was not an oop.

        Examining the resulting core file the value that was being triggering the assert was 0xd which may possibly be a mark word of an oop.

              Assignee:
              John Cuthbertson
              Reporter:
              John Cuthbertson
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved:
                Imported:
                Indexed: