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

Investigate memory access C2 optimizations

    XMLWordPrintable

Details

    Description

      The var-handle based memory access API is currently slower than a plain Unsafe access. This seems to be caused by two factors:

      * the JIT has trouble in hoisting Scope liveness checks outside a loop

      * when addresses are non-constant (e.g. because memory is allocated and accessed inside a try-with-resources), it seems like bound checks are also not optimized.

      Attachments

        Issue Links

          relates to

          Enhancement - null JDK-8226411 C2: Avoid memory barriers around off-heap unsafe accesses

          • P3 - Major loss of function.
          • Resolved

          Enhancement - null JDK-8235143 C2: No memory state needed in Thread::currentThread() intrinsic

          • P3 - Major loss of function.
          • Resolved

          JEP - Java Enhancement Proposal JDK-8132243 Optimize Final Field Loads In Generated Code

          • P3 - Major loss of function.
          • Draft

          Activity

            People

              jvernee Jorn Vernee
              mcimadamore Maurizio Cimadamore
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: