JDK-8186837 : Memory ordering nmethod, _state and _stack_traversal_mark
- Type: Bug
- Component: hotspot
- Sub-Component: runtime
- Affected Version: 10
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- Submitted: 2017-08-28
- Updated: 2017-09-16
- Resolved: 2017-08-31
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 10 |
|---|
10 b23Fixed  |
Related Reports
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
Description
The issue 8180932 - Parallelize safepoint cleanup changed _stack_traversal_mark to load acquire/store release, this is half wrong. The acquire part on read, loadload, is needed. But for simplicity the write side storestore fence should be match with loadload on read side and the changes to _stack_travel_mark undone.