RFR: 8356289: Shenandoah: Clean up SATB barrier runtime entry points
William Kemper
wkemper at openjdk.org
Wed Aug 20 20:58:36 UTC 2025
On Wed, 20 Aug 2025 20:18:21 GMT, Kelvin Nilsen <kdnilsen at openjdk.org> wrote:
>> The runtime entry points for the SATB slow-paths currently take a JavaThread* argument. When @rkennke did the entry points for Graal ([JDK-8356075](https://bugs.openjdk.org/browse/JDK-8356075)), he figured that we do not really need them. The slow-path is only called rarely (whenever the local SATB buffer is full), and getting the current Thread* in the runtime would not be the expensive part.
>>
>> This PR is a patch to do that clean up. The changes were tested on Linux x64/aarch64 with JTREG tier1-3 using Shenandoah for all tests.
>
> Looks good to me. Have we run this change through our internal CI regression pipelines?
Looks reasonable to me. I have the same question as @kdnilsen .
-------------
PR Comment: https://git.openjdk.org/jdk/pull/26850#issuecomment-3208064052
More information about the shenandoah-dev
mailing list