JDK-8035330 : Remove G1ParScanPartialArrayClosure and G1ParScanHeapEvacClosure
- Type: Enhancement
- Component: hotspot
- Sub-Component: gc
- Affected Version: 8u20,9
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- Submitted: 2014-02-19
- Updated: 2014-08-28
- Resolved: 2014-03-17
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 b08Fixed |
Related Reports
|
Relates :
|
Description
Above mentioned "closures" are in reality just methods (do_oop_nv()) wrapped into the Closure abstraction. This confuses readers, and adds lots of boiler plate code (closure definition and instantiations) in the process. Also for whatever reason, G1ParScanHeapEvacClosure is part of the specializations for oop_oop_iterate() (probably because of the confusion). Move them to G1ParScanThreadState which is the only place where they are referenced as methods. This also allows small optimizations.