JDK-8231086 : Shenandoah: Stronger invariant for object-arraycopy
- Type: Enhancement
- Component: hotspot
- Sub-Component: gc
- Affected Version: 8-shenandoah,11-shenandoah,14
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2019-09-16
- Updated: 2021-01-20
- Resolved: 2019-09-18
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 14 |
|---|
14 b15Fixed  |
Related Reports
|
Blocks :
|
|
|
Blocks :
|
|
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
Sub Tasks
|
JDK-8237012 :
|
Description
Currently, arraycopy operations can cause temporary from-space-references in the destination array. Those would be subsequently updated by an arraycopy-post-barrier, but it's awkward because this temporary from-space references need to be dealt with, e.g. in the CAS-obj barrier, and a few other places. We can update the src array before copying, and therefore ensure to never see a from-space-reference in the dst array, ever. This opens up a couple of opportunities for simplification and optimization.
Comments
|