RFR: 8368303: AlwaysAtomicAccesses is excessively strict

Mon Sep 22 21:56:05 UTC 2025

On Mon, 22 Sep 2025 16:51:08 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.

This flag also affects C2 - or did when it was introduced. Seems to me this flag is not really serving any useful purpose though - the JMM updates it was supposed to support evaluation of never eventuated.

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

PR Comment: https://git.openjdk.org/jdk/pull/27432#issuecomment-3321609544