------- Comment #11 from tdragon at tdragon dot net 2007-06-20 15:35 ------- Not sure if this is relevant or just GCC working differently on my target system, but I don't encounter the bug using -fstrict-aliasing, or in fact using individually the entire set of options under -O and -O2 on http://gcc.gnu.org/onlinedocs/gcc-4.2.0/gcc/Optimize-Options.html -- only when I specifically use the option "-O2".
i.e. "gcc -fstrict-aliasing -c alias1.c" DOESN'T, for me, cause the bug but "gcc -O2 -c alias1.c" DOES. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32328
