On Friday 16 December 2005 23:07, Aric Cyr wrote: > Last time I checked gcc doesn't enable optimizations unless a -O option is > specified explicitly (don't know if this has changed though).
I realize it is a moot point wrt the topic, but as you may know, there's an easy way to check. Running sh$ echo 'main () {}' > bloated.c sh$ gcc -v -Q $CFLAGS bloated.c will, amongst other things, dump exactly what optimizations (in terms of atomic gcc command-line optimizations) are used given the current setup and CFLAGS environment variable. My 3.4.4 does indeed do exactly the same thing with "-g" and "-g -O0". -- gmt