JDK-8267953 : restore 'volatile' to ObjectMonitor::_owner field
- Type: Bug
- Component: hotspot
- Sub-Component: runtime
- Affected Version: 17
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2021-05-28
- Updated: 2025-01-29
- Resolved: 2021-05-29
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 17 |
|---|
17 b25Fixed  |
Related Reports
|
Relates :
|
|
|
Relates :
|
Description
The following RFE:
JDK-8238174 migrate ObjectMonitor::_owner field away from C++ volatile semantics
removed 'volatile' from the ObjectMonitor::_owner field.
However, subsequent discussions concluded that we are
going to leave 'volatile' on fields that are racy so that the
reader has a clear indicator about the racy state of the field.
Comments
|