--- Comment #3 from gmorin1 at bloomberg dot net 2009-11-30 22:06 ---
The trunk g++ output looks good. As I said, there is a simple workaround. But
since this is a regression from 4.1, a fix in 4.4 would be nice.
Additionally, it would be great if you could document the full scope of t
--- Comment #2 from hubicka at gcc dot gnu dot org 2009-11-30 17:29 ---
With 4.5 we seem to be all fine here:
j...@gcc17:~/trunk/build/gcc$ ./g++ -B ./ -O2 tt.c -fdump-tree-all-details -S
-fdump-rtl-all-details-blocks
j...@gcc17:~/trunk/build/gcc$ more tt.s
.file "tt.c"
--- Comment #1 from gmorin1 at bloomberg dot net 2009-11-30 17:00 ---
I can see this problem with 4.3.2 (Debian 4.3.2-1.1), 4.2.4 (Debian 4.2.4-6),
4.4.0 20090514 (Red Hat 4.4.0-6). I do not see it with 4.1.2 20080704 (Red Hat
4.1.2-46) and 4.1.3 20080704 (prerelease) (Debian 4.1.2-25).
