JDK-8367014 : Rename class Atomic to AtomicAccess
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: runtime
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2025-09-05
  • Updated: 2025-09-23
  • Resolved: 2025-09-12
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.
JDK 26
26 b16Fixed
Related Reports
Blocks :  
JDK-8367013 - Add Atomic to package/replace idiom of volatile var plus AtomicAccess:: operations
Relates :  
JDK-8367501 - RISC-V: build broken after JDK-8365926
Relates :  
JDK-8367796 - Rename AtomicAccess gtests
Description
In order to free up the `Atomic` name for use as a template type (JDK-8367013), the existing all-static `Atomic` class needs to be renamed.

This involves changing the class name, changing all the uses, changing the header file name, and changing all the includes of that file.
Comments
Changeset: 9e843f56 Branch: master Author: Kim Barrett <kbarrett@openjdk.org> Date: 2025-09-12 06:35:55 +0000 URL: https://git.openjdk.org/jdk/commit/9e843f56ec0e4126e8256dff44f47c56e5282d20
12-09-2025
A pull request was submitted for review. Branch: master URL: https://git.openjdk.org/jdk/pull/27135 Date: 2025-09-08 06:26:03 +0000
08-09-2025