JDK-8245236 : Remove MO_VOLATILE Access decorator
- Type: Enhancement
- Component: hotspot
- Sub-Component: gc
- Affected Version: 11,15
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- Submitted: 2020-05-18
- Updated: 2021-08-18
- Resolved: 2020-05-20
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.
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 15 |
|---|
15 b24Fixed  |
Related Reports
|
Relates :
|
Description
The MO_VOLATILE Access decorator is provided to support C++ volatile loads and stores. However, (nearly?) all uses assume non-word-tearing semantics, which is equivalent to MO_RELAXED (Atomic relaxed load/store). So there's really no benefit to having MO_VOLATILE as a separate memory ordering decorator. We should be using MO_RELAXED instead, and can then remove MO_VOLATILE.
Comments
|