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

Code paths from oop_iterate() must use barrier-free access

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved
    • P4
    • Resolution: Fixed
    • 11, 12
    • 12
    • hotspot
    • gc
    • b09
    • generic
    • generic

    Description

      We have several code paths going out from oop_iterate() methods that lead to GC barriers. This is not only inefficient but outright wrong. oop_iterate() is normally used by GC and GC need to see the raw stuff, not some resolved objects. In Shenandoah's full-GC it's fatal to attempt to read objects's forwarding pointers, because it's temporarily pointing to nowhere land.

      Attachments

        Issue Links

          relates to

          Enhancement - null JDK-8221766 Load-reference barriers for Shenandoah

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

          Enhancement - null JDK-8217325 Enable inlining of java_lang_Class::oop_size_raw

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

          Enhancement - null JDK-8271939 Clean up primitive raw accessors in oopDesc

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

          Activity

            People

              rkennke Roman Kennke
              rkennke Roman Kennke
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: