http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54743
--- Comment #4 from Paolo Carlini 2012-09-29
08:08:32 UTC ---
The condition is always to true thus the signed integer overflows and anything
can happen, maybe something different for different release series or at the
different optimizatio
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54743
--- Comment #3 from 顏烈彬 2012-09-29 07:49:12 UTC ---
(In reply to comment #1)
You mean that i (as most INT_MAX) is always less than 300L?
And, in a RH 2.6.18-164.el5, gcc Red Hat 4.1.2-52, it runs as (was) expected,
because it's buggy is g
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54743
--- Comment #2 from 顏烈彬 2012-09-29 07:48:26 UTC ---
(In reply to comment #1)
You mean that i (as most INT_MAX) is always less than 300L?
And, in a RH 2.6.18-164.el5, gcc Red Hat 4.1.2-52, it runs as (was) expected,
because it's buggy is g
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54743
Andreas Schwab changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|