-
Enhancement
-
Resolution: Won't Fix
-
P4
-
None
-
hs21
-
generic
-
generic
Many of the cardtable interfaces and class hierarchy were designed
at a time when HotSpot was still growing up and designed as a vehicle
for research and evolution. This has, however, resulted in much avoidable
cruft and convoluted class hierarchies that serve no real purpose
in a commercial product JVM. They make code comprehension and
maintenance expensive and can also make finding, diagnosing and
finding bugs difficult, as well as leaving performance on the table.
This CR is aimed at cleaning up this accumulated cruft from the
classes. See comments section for the specific details.
at a time when HotSpot was still growing up and designed as a vehicle
for research and evolution. This has, however, resulted in much avoidable
cruft and convoluted class hierarchies that serve no real purpose
in a commercial product JVM. They make code comprehension and
maintenance expensive and can also make finding, diagnosing and
finding bugs difficult, as well as leaving performance on the table.
This CR is aimed at cleaning up this accumulated cruft from the
classes. See comments section for the specific details.
- relates to
-
JDK-6883834 ParNew: assert(!_g->to()->is_in_reserved(obj),"Scanning field twice?") with LargeObjects tests
- Closed
-
JDK-7036482 clear argument is redundant and unused in cardtable methods
- Closed
-
JDK-7037276 Unnecessary double traversal of dirty card windows
- Closed
-
JDK-8139800 Remove OopsInGenClosure
- Resolved