RFR: 8358568: Purge obsolete/broken GenerateSynchronizationCode flag [v5]
duke
duke at openjdk.org
Sat Jul 5 06:34:51 UTC 2025
On Fri, 4 Jul 2025 06:43:02 GMT, hanguanqiang <duke at openjdk.org> wrote:
>> This PR fixes JDK-8358568, a JVM crash triggered when running with -XX:-GenerateSynchronizationCode
>>
>> Problem:
>> When synchronization code generation is disabled by -XX:-GenerateSynchronizationCode, the compiler’s do_monitor_exit() method still tries to access monitor objects without checking if any monitors exist.This causes an assertion failure and JVM crash.
>>
>> Root Cause:
>> Parse::do_monitor_exit() calls shared_unlock() using monitor info unconditionally,but with GenerateSynchronizationCode disabled, no monitor info is available, leading to invalid access.
>>
>> Fix
>> Purge obsolete/broken GenerateSynchronizationCode flag
>
> hanguanqiang has updated the pull request incrementally with one additional commit since the last revision:
>
> correct an error
>
> correct an error
@hgqxjj
Your change (at version 6ebc2ecb7b41da558a26400461b2e8084e915c3d) is now ready to be sponsored by a Committer.
-------------
PR Comment: https://git.openjdk.org/jdk/pull/26108#issuecomment-3038269276
More information about the hotspot-compiler-dev
mailing list