G1ScanEvacuatedObjClosure needs to be told where the object that is scanned is located (young/old) to properly handle additions to the remembered sets.
Currently we call a method on G1ScanEvacuatedObjClosure to do so, but it would be better to use an RAII object that automatically sets and resets it. With an additional "Uninitialized" state, basic checking whether the value has been set to find bugs can be implemented easily too.
Suggested by ~kbarrett in the review thread forJDK-8212911.
Currently we call a method on G1ScanEvacuatedObjClosure to do so, but it would be better to use an RAII object that automatically sets and resets it. With an additional "Uninitialized" state, basic checking whether the value has been set to find bugs can be implemented easily too.
Suggested by ~kbarrett in the review thread for
- is blocked by
-
JDK-8212911 Unify and micro-optimize handling of non-in-collection set references in oop closures
-
- Resolved
-
- relates to
-
-
- Open
-