JDK-8260106 : Shenandoah: refactor reference updating closures and related code
- Type: Enhancement
- Component: hotspot
- Sub-Component: gc
- Affected Version: 8-shenandoah,11.0.9,16,17
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- Submitted: 2021-01-20
- Updated: 2021-02-04
- Resolved: 2021-01-27
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 17 |
|---|
17 b08Fixed  |
Related Reports
|
Blocks :
|
|
|
Relates :
|
Description
We have a block in ShenandoahHeap::maybe_update_heap_refs that is irrelevant after JDK-8231086. Additionally, "resolve and update" paths are really only used by STW GCs, and thus do not require atomic updates. This leads to considerable simplifications in the code, and improves performance on the common paths (especially in fastdebug builds that drop many irrelevant asserts).
Comments
|