-
Bug
-
Resolution: Fixed
-
P4
-
11, 12
-
b09
-
generic
-
generic
We have several code paths going out from oop_iterate() methods that lead to GC barriers. This is not only inefficient but outright wrong. oop_iterate() is normally used by GC and GC need to see the raw stuff, not some resolved objects. In Shenandoah's full-GC it's fatal to attempt to read objects's forwarding pointers, because it's temporarily pointing to nowhere land.
- relates to
-
JDK-8221766 Load-reference barriers for Shenandoah
-
- Resolved
-
-
JDK-8217325 Enable inlining of java_lang_Class::oop_size_raw
-
- Resolved
-
-
JDK-8271939 Clean up primitive raw accessors in oopDesc
-
- Resolved
-