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

Shenandoah: Don't produce new memory state in C2 LRB runtime call

    XMLWordPrintable

    Details

    • Subcomponent:
      gc
    • Resolved In Build:
      b26
    • CPU:
      generic
    • OS:
      generic

      Description

      The runtime call in expanded Shenandoah LRB doesn't need to produce (and consume) raw memory state. I believe this is a left-over from when the LRB (or WB) allocated from TLABs, and would mess with TLAB pointers, when not ordered correctly. (Also, we used to require ordering with RBs back when we had them, but we already removed that memory dependency on -8 offset)

        Attachments

          Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. JDK-8277652 SIGSEGV in ShenandoahBarrierC2Support::verify_raw_mem for malformed control flow graph

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

          Bug - A problem which impairs or prevents the functions of the product. JDK-8287227 Shenandoah: A couple of virtual thread tests failed with iu mode even without Loom enabled.

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

          Commit Commit openjdk/jdk/3d39f09c

          Review Review openjdk/jdk/6526

            Activity

              People

              Assignee:
              rkennke Roman Kennke
              Reporter:
              rkennke Roman Kennke
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: