ShenandoahOptimizeFinals is an illegal optimization

[Roman Kennke]

Am 18.10.2017 um 16:06 schrieb Roland Westrelin:
>> and keep it always-on for static finals? or is that not safe? I mean, it
>> *is* possible to mess with static finals using JNI/reflection too, right?
> If we keep ShenandoahOptimizeFinals, then we need another option for
> static final fields and stable arrays?
>
> Roland.

FWIW, I seem to get failures (NPEs) in the compiler.compiler benchmark 
when running it on to-gc1, fairly consistently. In two runs with -ShOF 
(and Roland's recent related patch) they did not happen. I haven't done 
enough testing and analysis to draw a connection, but it seems necessary 
to look at it more closely.

Roman