-
Enhancement
-
Resolution: Fixed
-
P4
-
None
-
b16
-
generic
-
generic
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8204416 | 11.0.1 | Kim Barrett | P4 | Resolved | Fixed | team |
In particular, for reference processing when discovery is not atomic, the case of a discovered reference which is later found to have been enqueued but still has a non-null referent is no longer possible. This means that much of the difference between pp2_work and pp2_work_concurrent_discovery is no longer required, and those functions can be mostly merged.
For the most part, the Reference.next field no longer needs any special treatment, and can be handled like any normal object field. It still requires some special handling in support of FinalReferences though; a non-null next is the mechanism used to indicate a FinalReference is no longer active, since the reference object is not cleared.
- backported by
-
JDK-8204416 Simplify reference processing in light of JDK-8175797
- Resolved
- blocks
-
JDK-8202845 Refactor reference processing for improved parallelism
- Resolved
- is blocked by
-
JDK-8193780 (ref) Remove the undocumented "jdk.lang.ref.disableClearBeforeEnqueue" system property
- Resolved
- relates to
-
JDK-8175797 (ref) Reference::enqueue method should clear the reference object before enqueuing
- Closed
-
JDK-8203848 Missing remembered set entry in j.l.ref.references after JDK-8203028
- Closed
-
JDK-8215985 ZGC: Simplify reference processing in light of JDK-8175797
- Resolved
(1 relates to)