ShenandoahOptimizeFinals is an illegal optimization
Roland Westrelin
rwestrel at redhat.com
Wed Oct 18 12:58:29 UTC 2017
> I wonder: if it's broken for instance fields, is it broken for static
> fields too, for the same reasons? Replace the constructor with the
> <clinit> in your example above and get the same problem, if the Class
> instance is evacuated during clinit ? Or is that not possible?
I'm not sure how that would break with static fields.
What about stable fields?
Also there could be well known classes for which we could leave this on
(such a String) because we know they are unaffected. Do we want to?
Roland.
More information about the shenandoah-dev
mailing list