RFR: 8216350: AArch64: monitor unlock fast path not called

Andrew Haley aph at redhat.com
Tue Jan 8 08:49:21 UTC 2019

On 1/8/19 8:03 AM, Nick Gasson (Arm Technology China) wrote:
> It seems that the unlock fast-path will only be executed when the 
> monitor was originally locked by the runtime (e.g. when the lock was 
> first inflated), because ObjectSynchronizer::slow_enter will store 
> markOopDesc::unused_mark into the dhw, and this value has bit #1 set.
> Can someone help me review this change to aarch64_enc_fast_lock to use 
> markOopDesc::unused_mark as the arbitrary non-null value rather than 
> `box' to match ObjectSynchronizer::slow_enter?

Thanks. How does this compare with the x86 code?

Andrew Haley
Java Platform Lead Engineer
Red Hat UK Ltd. <https://www.redhat.com>
EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671

More information about the hotspot-compiler-dev mailing list