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

[REDO] 8297487: G1 Remark: no need to keep alive oop constants of nmethods on stack

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Fixed
    • P4
    • 21
    • 20
    • hotspot
    • gc
    • b05

    Description

      The issues that caused the BACKOUT were solved with JDK-8300915.
      See also https://mail.openjdk.org/pipermail/hotspot-gc-dev/2023-January/041194.html
      --
      The stackwalks to keep alive oops of nmethods found on stack during G1 remark seem redundant as nmethod entry barriers do the job already: https://github.com/openjdk/jdk/blob/f26bd4e0e8b68de297a9ff93526cd7fac8668320/src/hotspot/share/gc/shared/barrierSetNMethod.cpp#L85

      Objects in the constant pool of a nmethod are weakly referenced. So G1 requires nmethod entry barriers to conservatively keep alive the constant objects for SATB during concurrent marking (see https://bugs.openjdk.org/browse/JDK-8288970).

      Attachments

        Issue Links

          Activity

            People

              rrich Richard Reingruber
              rrich Richard Reingruber
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: