RFR: 8373116: Genshen: arraycopy_work should be done unconditionally by arraycopy_marking if the array is in an old region [v5]
Xiaolong Peng
xpeng at openjdk.org
Fri Dec 5 23:34:56 UTC 2025
On Fri, 5 Dec 2025 23:19:54 GMT, William Kemper <wkemper at openjdk.org> wrote:
> At step 2, we have an element in the old array pointing to young, correct? Why is it not represented in the remembered set at the beginning of young mark? If it is because the old -> young pointer was created _after_ init mark, then the young pointer was either reachable when mark started, or it was created after mark started. Either way, the young pointer should have been found without this SATB modification. Unless, it was in the remembered set, but it didn't get scanned because a mutator modified it before it was scanned.
array copy involves two array object, src and dst. The dst array is an old array, the src may not be an old, it could be young.
-------------
PR Comment: https://git.openjdk.org/jdk/pull/28669#issuecomment-3618958253
More information about the shenandoah-dev
mailing list