RFR: 8368303: AlwaysAtomicAccesses is excessively strict [v4]

Aleksey Shipilev shade at openjdk.org
Mon Oct 6 16:05:45 UTC 2025


On Mon, 6 Oct 2025 15:31:02 GMT, Andrew Haley <aph at openjdk.org> wrote:

>> 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 satisfy `AlwaysAtomicAccesses`. 
>> 
>> We need this in order to allow progress on JDK-8365147.
>
> Andrew Haley has updated the pull request incrementally with one additional commit since the last revision:
> 
>   Update src/hotspot/share/gc/shared/c1/barrierSetC1.cpp
>   
>   Co-authored-by: Dean Long <17332032+dean-long at users.noreply.github.com>

Marked as reviewed by shade (Reviewer).

-------------

PR Review: https://git.openjdk.org/jdk/pull/27432#pullrequestreview-3305691185


More information about the hotspot-dev mailing list