JDK-8035329 : Move G1ParCopyClosure::copy_to_survivor_space into G1ParScanThreadState
- Type: Enhancement
- Component: hotspot
- Sub-Component: gc
- Affected Version: 8u20,9
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- Submitted: 2014-02-19
- Updated: 2016-01-05
- Resolved: 2014-02-24
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 8 | JDK 9 |
|---|---|
8u20Fixed  |
9 b04Fixed |
Related Reports
|
Relates :
|
|
|
Relates :
|
Description
G1ParCopyClosure::copy_to_survivor_space seems wrongly placed in G1ParCopyClosure: - the method does not depend on any template parameter, increasing code size - it references G1ParScanThreadState a lot Due to that, G1ParScanThreadState seems a good target to move the method to.