Details
Description
I was following up on performance testing results for JDK-8260106, and realized that there are ShenandoahMarkContext::mark_strong called from mark_work_loop. It was supposed to be inlined. I believe it is a simple omission after JDK-8255019 moved mark_work_loop code to shenandoahMark.cpp.
Attachments
Issue Links
- blocks
-
JDK-8260106 Shenandoah: refactor reference updating closures and related code
-
- Resolved
-
- relates to
-
JDK-8255019 Shenandoah: Split STW and concurrent mark into separate classes
-
- Resolved
-