-
Enhancement
-
Resolution: Fixed
-
P4
-
8-shenandoah, 11-shenandoah, 13, 14, 15
-
b15
-
generic
-
generic
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8243599 | 14.0.2 | Roman Kennke | P4 | Resolved | Fixed | b04 |
Currently, we set the safe-iteration-limit at start of update-refs-phase. This is subsequently used as limit for the linear scan in update-refs phase. However, with the strong invariant we can do better: we can set this limit at evac-start, because it is guaranteed that any reference that is written to the new fields is to-space and does not require updating.
An exception is new allocations for evacuated objects: those still require updates and thus require special handling.
An exception is new allocations for evacuated objects: those still require updates and thus require special handling.
- backported by
-
JDK-8243599 Shenandoah: Avoid updating new regions from start of evacuation
-
- Resolved
-
- relates to
-
JDK-8240873 Shenandoah: Short-cut arraycopy barriers
-
- Resolved
-
-
JDK-8241534 Shenandoah: region status should include update watermark
-
- Resolved
-
-
JDK-8243291 Shenandoah: no need to retire TLABs at Init Update Refs
-
- Resolved
-
-
JDK-8247860 Shenandoah: add update watermark line in rich assert failure message
-
- Resolved
-