------- Comment #12 from bouzim at gmail dot com 2010-03-05 22:01 ------- Current gcc-4_4-branch shows this buggy behavior, and I can confirm that it goes away after applying the one-line fix in gcc/tree-complex.c as stated by H.J. Lu. Neither gcc 4.3.x nor gcc 4.5 have this bug, can it please be fixed in gcc-4_4-branch?
-- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43251
