question about -fno-optimize-static-class-initialization

Sun Dec 2 18:03:00 GMT 2001

Tom Tromey wrote:
>Bryce> Or, perhaps once we get tree based inlining, we can run a
>Bryce> rudundant class initialization elimination pass after the
>Bryce> inlining is done and avoid this issue.
>>Do you mean by doing some kind of flow analysis to see for ourselves
>when the call is redundant? Or do you mean continuing to use a local
>state variable but then unifying this variable with the inlined code?
>The latter problem could be solved by using a higher-level
>representation for class init calls and then lowering it after
>inlining.
>
I guess we can just do a pass to insert the local variable and the 
checks after tree inlining is done.
Another option is to make use of the definate assignment code, but I 
suspect Java's definate assignment rules arn't as complete as those of 
the optimzier - ie the optimizer may be able to remove the checks in 
more circumstances.
regards
Bryce.