JDK-8254264 : Remove redundant cross_modify_fence()
- Type: Enhancement
- Component: hotspot
- Sub-Component: runtime
- Affected Version: 16
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- Submitted: 2020-10-08
- Updated: 2020-10-28
- Resolved: 2020-10-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 16 |
|---|
16 b21Fixed  |
Related Reports
|
Relates :
|
|
|
Relates :
|
Description
Remove cross_modify_fence() from ~ThreadBlockInVM(), ~ThreadBlockInVMWithDeadlockCheck() and java_suspend_self_with_safepoint_check(). These fences were added before each JavaThread had to disarm itself (JDK-8230594). After a safepoint/handshake each JavaThread will always call SafepointMechanism::process_if_requested_slow() when transitioning out of the safe state and will execute a cross_modify_fence().
Comments
|