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

[Alexandre Petit-Bianco <apbianco at cygnus dot com>]

Per Bothner writes:

> One big piece is that it appears that the code for
> -fno-optimize-static-class-initialization seems to be conncted with
> the definitive assignment code

Have you read this?

  http://gcc.gnu.org/ml/java/2001-08/msg00014.html

Basically we attach local booleans to static class initialization and
we let the definite assignment code figure whether a class is
definitely initialized within a static method. Constant propagation
helps us getting rid if the unnecessary -- at the end of the method
body walk, we know which class(es) a method is known to definitely
initialize and we use the information when appropriate.

Does this help? 

./A