--- Comment #4 from manu at gcc dot gnu dot org 2010-09-02 22:50 ---
CCP is responsible for this.
*** This bug has been marked as a duplicate of 18501 ***
--
manu at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #3 from tadhunt at gmail dot com 2010-09-02 16:08 ---
(In reply to comment #2)
Richard, thanks for the confirmation.
This is a great feature that we've come to rely on over the years for catching
rookie errors.
This might not appear in comments very often, but I appreciate
--- Comment #2 from rguenth at gcc dot gnu dot org 2010-09-02 09:12 ---
It's just optimized to always print 10 and the maybe-uninitialized warning
code runs too late.
A dup of some other PR.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45493
--- Comment #1 from tadhunt at gmail dot com 2010-09-02 03:42 ---
Same behavior on 4.4.3 & 4.4.1 (same host, target & build)
Forgot to mention:
gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu5)
gcc version 4.4.1 (Ubuntu 4.4.1-4ubuntu9)
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=4549
