Integrated: 8288282: Zero-release build is broken after JDK-8279047 due to UseHeavyMonitors is read-only

Jie Fu jiefu at openjdk.java.net
Mon Jun 13 14:42:09 UTC 2022


On Sat, 11 Jun 2022 15:08:38 GMT, Jie Fu <jiefu at openjdk.org> wrote:

> Hi all,
> 
> Zero-release build is broken after JDK-8279047.
> After JDK-8279047, `UseHeavyMonitors` becomes read-only in PRODUCT VMs.
> 
> But for Zero, `UseHeavyMonitors` needs to be reset if `DiagnoseSyncOnValueBasedClasses != 0`.
> 
>   // If lock diagnostics is needed, always call to runtime
>   if (DiagnoseSyncOnValueBasedClasses != 0) {
>     FLAG_SET_DEFAULT(UseHeavyMonitors, true);
>   }
> 
> 
> I never hear that people would DiagnoseSyncOnValueBasedClasses with zero vms.
> So in order to expire `UseHeavyMonitors` for all PRODUCT VMs, I suggest disabling lock diagnostics for zero vms.
> 
> Thanks.
> Best regards,
> Jie

This pull request has now been integrated.

Changeset: 4aede33f
Author:    Jie Fu <jiefu at openjdk.org>
URL:       https://git.openjdk.org/jdk/commit/4aede33fbf940290bb86ac1af1e833ce4d709100
Stats:     6 lines in 2 files changed: 2 ins; 0 del; 4 mod

8288282: Zero-release build is broken after JDK-8279047 due to UseHeavyMonitors is read-only

Reviewed-by: dholmes, shade

-------------

PR: https://git.openjdk.org/jdk/pull/9138


More information about the hotspot-dev mailing list