Biased locking Obsoletion

Patricio Chilano patricio.chilano.mateo at oracle.com
Tue Nov 3 21:08:34 UTC 2020


Hi all,

As discussed in 8231264, the idea was to switch biased locking to false 
by default and deprecate all related flags with the intent to remove the 
code in a future release unless compelling evidence showed that the code 
is worth maintaining.
I see there is only one issue that was filed since biased locking was 
disabled by default (https://github.com/openjdk/jdk/pull/542) that seems 
to have been addressed. As per 8231264 change, the code was set to be 
obsoleted in 16, so we are already in a position to remove biased 
locking code unless there are arguments for the contrary. The 
alternative would be to give more time and move biased locking 
obsoletion to a future release.
Let me know your thoughts.

Thanks,

Patricio


More information about the hotspot-runtime-dev mailing list