Refactor oops in JNI to use the Access API

XMLWordPrintable

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

      JNI has weak and strong off-heap references to oops. Today the weak semantics is manages using explicit calls to G1 SATB enqueue barriers. Today the strong semantics simply assume processing in a stop-the-world phase (either STW collection or an STW initial mark).

      Now that the Access API is available, it should be used instead.

            Assignee:
            Kim Barrett
            Reporter:
            Kim Barrett
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: