JDK-8245594 : Remove volatile-qualified member functions and parameters from oop class
- Type: Enhancement
- Component: hotspot
- Sub-Component: runtime
- Affected Version: 15
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- Submitted: 2020-05-21
- Updated: 2024-09-28
- Resolved: 2020-05-25
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 b25Fixed  |
Related Reports
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
Description
The oop class and its subclasses are made more complicated by the presence of volatile qualified member functions and parameters. Those overloads exist to support operations on volatile oop values. But such values exist as the conventional mechanism for noting a variable is accessed by multiple threads and needs special handling. The intended semantics for these bare volatile variable accesses is really relaxed atomic, and it would be better to actually use such. Doing so would eliminate the need for the volatile qualifications in the member functions.
Comments
|