--- Comment #5 from sam at gcc dot gnu dot org 2008-05-12 21:24 ---
Indeed, I missed the "not" in your message :)
This is great news. Closing.
--
sam at gcc dot gnu dot org changed:
What|Removed |Added
-
--- Comment #4 from anhvofrcaus at gmail dot com 2008-05-12 15:19 ---
Sam,
If you look at my comment on 21 January 2008. This problem was fixed starting
with gcc-4.3-20080118. That is why you did not see the problem existed. In
summary, this PR should be closed around that time.
--
--- Comment #3 from sam at gcc dot gnu dot org 2008-05-12 14:12 ---
What compilation option did you use? I cannot reproduce this with Debian's 4.3
compiler or with current SVN trunk.
--
sam at gcc dot gnu dot org changed:
What|Removed |Added
--
--- Comment #2 from anhvofrcaus at gmail dot com 2008-01-21 21:54 ---
This problem does not occur in gcc-4.3-20080118.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33457
--- Comment #1 from anhvofrcaus at gmail dot com 2007-09-17 22:13 ---
Sorry for the typo in problem description paragraph. What I mean was if line 11
commented out and line 12 uncommented, the codes behave properly.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33457