------- Comment #13 from atgraham at gmail dot com 2006-08-11 02:42 ------- The problem goes away (at least in this case) at optimization levels -O[s123] (but remains at -O0) when compiling with -fstack-protector. Of course, that's not really an acceptable workaround for most people affected by this problem.
-- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28493
