ShenandoahOptimizeFinals is an illegal optimization

Aleksey Shipilev shade at redhat.com
Wed Oct 18 13:36:56 UTC 2017


On 10/18/2017 03:32 PM, Christine Flood wrote:
> IThe safe thing in my mind is to just have ShenandoahOptimizeFinals always default to false. 
> 
> We don't want the appearance of incompatibility even if we are legally within the letter of the law.

This is exactly the story with TrustFinalNonStaticFields: that optimization is legal, but some code
is broken, and this is why TrustFinalNonStaticFields is experimental and defaults to "false". Yet
there are users who enable +TFNSF for their workloads to reap performance benefits. I think it makes
sense to piggyback on that option for our similar optimization too.

-Aleksey



More information about the shenandoah-dev mailing list