JDK-8025305 : Cleanup CardTableModRefBS usage in G1
- Type: Bug
- Component: hotspot
- Sub-Component: gc
- Affected Version: hs25
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- Submitted: 2013-09-24
- Updated: 2014-10-15
- Resolved: 2013-09-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 7 | JDK 8 | Other |
|---|---|---|
7u60Fixed  |
8Fixed |
hs25Fixed |
Description
CardTableModRefBS contains a bunch of G1 specific code. G1CollectedHeap has two pointers to the same BarrierSet instance and has a lot of downcasts from BarrierSet to CardTableModRefBS, but G1 will only ever work with G1SATBCardTableModRefBS. The fix for JDK-8014555 will be much cleaner if we move some G1 specific code from CardTableModRefBS to G1SATBCardTableModRefBS.
Comments
|