JDK-8368303 : AlwaysAtomicAccesses is excessively strict
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 26
  • Priority: P3
  • Status: Open
  • Resolution: Unresolved
  • OS: generic
  • CPU: generic
  • Submitted: 2025-09-22
  • Updated: 2025-09-22
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
tbdUnresolved
Related Reports
Blocks :  
JDK-8365147 - AArch64: Replace DMB + LD + DMB with LDAR for C1 volatile field loads
Relates :  
JDK-8033380 - Experimental VM flag to enforce access atomicity
Description
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.
Comments
A pull request was submitted for review. Branch: master URL: https://git.openjdk.org/jdk/pull/27432 Date: 2025-09-22 16:51:08 +0000
22-09-2025