JDK-8179261 : Replace always_update_barrier_set with proper API in BarrierSet
- Type: Enhancement
- Component: hotspot
- Sub-Component: gc
- Affected Version: 10
- Priority: P4
- Status: Closed
- Resolution: Withdrawn
- OS: generic
- CPU: generic
- Submitted: 2017-04-25
- Updated: 2017-04-26
- Resolved: 2017-04-26
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 |
|---|
10Resolved  |
Related Reports
|
Relates :
|
Description
There's a global variable always_update_barrier_set that directs whether or not oop stores and its GC barriers require a release membar. It is only used for CMS. It should be refactored into a proper API in BarrierSet, so that this GC specific hook can be avoided in shared code, and instead be implemented by GCs that need it.
Comments
|