AlwaysAtomicAccesses is excessively strict

XMLWordPrintable

    • Type: Enhancement
    • Resolution: Fixed
    • Priority: P3
    • 26
    • Affects Version/s: 26
    • Component/s: hotspot
    • b19
    • generic
    • generic

      In C1, the experimental flag AlwaysAtomicAccesses treats accesses to all fields as if they were volatile fields. This is correct but excessive: we only need single-copy atomicity to satisfyAlwaysAtomicAccesses.

            Assignee:
            Andrew Haley
            Reporter:
            Andrew Haley
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: