Details
-
Enhancement
-
Resolution: Fixed
-
P4
-
20
-
b05
-
Fix failed
Description
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).
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).
Attachments
Issue Links
- is blocked by
-
JDK-8291302 ARM32: nmethod entry barriers support
-
- Resolved
-
- is cloned by
-
JDK-8302462 [REDO] 8297487: G1 Remark: no need to keep alive oop constants of nmethods on stack
-
- Resolved
-
- relates to
-
JDK-8288970 G1 does not keep weak nmethod oops alive
-
- Resolved
-
-
JDK-8299956 [BACKOUT] 8297487: G1 Remark: no need to keep alive oop constants of nmethods on stack
-
- Closed
-
-
JDK-8290025 Remove the Sweeper
-
- Resolved
-
(2 links to)