On Wed, 19 Aug 2026 01:37:39 GMT, David Holmes <[email protected]> wrote:
>> src/hotspot/cpu/aarch64/sharedRuntime_aarch64.cpp line 2056: >> >>> 2054: // VM thread changes sync state to synchronizing and suspends >>> threads for GC. >>> 2055: // Thread A is resumed to finish this native method, but >>> doesn't block here since it >>> 2056: // didn't see any synchronization is progress, and escapes. >> >> I think the comment is still relevant even if we now switch to the in-vm >> state to achieve it rather than the native-trans state. > > Or maybe the comment is already stale? I believe it is very stale but was blindly copied to new ports. I tried to remove all occurrences to avoid further confusion. It describes a pathological scenario that was possible with the ancient suspend/resume algorithm. The current algorithm needs only to be in an unsafe state, which in practice simply means not native and not blocked. ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/32415#discussion_r3810107960
