comiler warnings

Dima Sorkin
Tue Dec 27 08:15:00 GMT 2005

On 12/25/05, Tom Emerson wrote:
> > for(unsigned i;i<10;++i){
> >     do something with "i";
> > }
> Presumably because with -g the uninitialized variable check isn't
> performed. The behavior of that code is undefined: you really want to
> be initializing that loop variable.

 Is it a compiler's bug that it doesn't warn about it in debug mode ?

Thank you,

More information about the Gcc-help mailing list