JDK-8189871 : Refactor GC barriers to use declarative semantics
- Type: Enhancement
- Component: hotspot
- Sub-Component: gc
- Affected Version: 10
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- Submitted: 2017-10-24
- Updated: 2021-08-19
- Resolved: 2017-11-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 10 |
|---|
10 b34Fixed  |
Related Reports
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
Description
Today, GC barriers or BarrierSet are called explicitly around accesses that require specific barriers. It would be desirable if instead accesses are annotated with declarative semantics. Instead of calling different barriers on BarrierSet in different situations explicitly that makes sense for some GCs and not others, this new approach should declare what property makes the access special and let the API automatically generate the correct barriers.
Comments
|