[Bug c++/22355] Multiple local static variables initialization: missed optimization opportunity

[yuri at Magma-DA dot COM]

------- Additional Comments From yuri at Magma-DA dot COM  2005-07-07 21:21 -------
Subject: Re:  Multiple local static variables initialization:
 missed optimization opportunity

I agree, this situation is fuzzy and bug is probably invalid.
But there are actually local static initializations that are to blame.

Why should these be checked/initialized on entry into the function, not 
globally?
Any particular benefit of this ?
I think it would have been way cleaner if initializations were done 
globally when code is loaded.

Yuri


pinskia at gcc dot gnu dot org wrote:

>------- Additional Comments From pinskia at gcc dot gnu dot org  2005-07-07 20:39 -------
>Say we call f() again before finish initializing i. then we call the get statement, it just undefined?
>
>  
>



-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22355