-
Type:
Enhancement
-
Resolution: Fixed
-
Priority:
P4
-
Affects Version/s: 20
-
Component/s: hotspot
-
b05
The issues that caused the BACKOUT were solved with JDK-8300915.
See also https://mail.openjdk.org/pipermail/hotspot-gc-dev/2023-January/041194.html
--
The stackwalks to keep alive oops of nmethods found on stack during G1 remark seem redundant as nmethod entry barriers do the job already: https://github.com/openjdk/jdk/blob/f26bd4e0e8b68de297a9ff93526cd7fac8668320/src/hotspot/share/gc/shared/barrierSetNMethod.cpp#L85
Objects in the constant pool of a nmethod are weakly referenced. So G1 requires nmethod entry barriers to conservatively keep alive the constant objects for SATB during concurrent marking (see https://bugs.openjdk.org/browse/JDK-8288970).
See also https://mail.openjdk.org/pipermail/hotspot-gc-dev/2023-January/041194.html
--
The stackwalks to keep alive oops of nmethods found on stack during G1 remark seem redundant as nmethod entry barriers do the job already: https://github.com/openjdk/jdk/blob/f26bd4e0e8b68de297a9ff93526cd7fac8668320/src/hotspot/share/gc/shared/barrierSetNMethod.cpp#L85
Objects in the constant pool of a nmethod are weakly referenced. So G1 requires nmethod entry barriers to conservatively keep alive the constant objects for SATB during concurrent marking (see https://bugs.openjdk.org/browse/JDK-8288970).
- clones
-
-
- Closed
-
- is blocked by
-
JDK-8300915 G1: incomplete SATB because nmethod entry barriers don't get armed
-
- Resolved
-
- relates to
-
-
- Closed
-
-
-
- Closed
-
-
-
- Resolved
-
(2 links to)