Refactor ciInstanceKlass G1 keep alive barrier to use Access API.

XMLWordPrintable

    • Type: Enhancement
    • Resolution: Fixed
    • Priority: P4
    • 11
    • Affects Version/s: None
    • Component/s: hotspot
    • None
    • gc
    • b01

      When creating a ciInstanceKlass handle, G1 might need a SATB barrier to keep "peeked" weak klass pointers alive during marking.
      This should now be done with the Access API instead of manual calls to the G1 SATB barrier.

            Assignee:
            Erik Österlund
            Reporter:
            Erik Österlund
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: