JDK-7016955 : G1: remove the is_zeroed parameter from the HeapRegion constructor
- Type: Enhancement
- Component: hotspot
- Sub-Component: gc
- Affected Version: hs21
- Priority: P5
- Status: Resolved
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2011-02-03
- Updated: 2013-09-18
- Resolved: 2012-09-25
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 | Other |
|---|---|
8Fixed  |
hs25Fixed |
Related Reports
|
Relates :
|
Description
The HeapRegion constructor takes an "is_zeroed" parameter that indicates whether the newly-allocated region is already zeroed. This is a hickup from the time when we had the concurrent zero fililng thread which has not been removed (6977804: G1: remove the zero-filling thread). It should have been removed as part of that CR but I just missed that extra parameter. It'd be good to get rid of it. Note that the is_zeroed parameter is propagated through several layers of constructors and initialization methods.
Comments
|