Clean up MutableCallSite to use explicit release fence instead of AtomicInteger

XMLWordPrintable

    • Type: Enhancement
    • Resolution: Fixed
    • Priority: P4
    • 24
    • Affects Version/s: None
    • Component/s: core-libs

      `Unsafe::storeFence` and `VarHandle::releaseFence` were added in JDK 8 and 9 respectively; `MutableCallSite` was implemented in JDK 7, 2 years before the Unsafe addition. We should move the MutableCallSite's `AtomicInteger.lazySet(0)` call to an explicit `UNSAFE.storeFence()` for consistency and clarity.

            Assignee:
            Chen Liang
            Reporter:
            Chen Liang
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: