JDK-8200429 : Adjust object pinning interface on CollectedHeap
- Type: Enhancement
- Component: hotspot
- Sub-Component: gc
- Affected Version: 11
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- Submitted: 2018-03-29
- Updated: 2018-04-19
- Resolved: 2018-04-04
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 11 |
|---|
11 b10Fixed  |
Related Reports
|
Blocks :
|
Description
The recent additions to CollectedHeap to support object pinning didn't quite fit the bill for what the Shenandoah folks had in mind. Instead of having CollectedHeap::pin_obejct/unpin_object grab/release the GCLocker when object pinning is not supported, we add a CollectedHeap::supports_obejct_pinning() and let the caller take the appropriate action based on the response.