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
Bug #: 54743
Summary: Large loop runs endingless
Classification: Unclassified
Product: gcc
Version: 4.6.3
Status: UNCONFIRMED
Severity: normal
Priority: P3
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53666
Bug #: 53666
Summary: -std=c++0x cause cc1plus to eat up RAM
Classification: Unclassified
Product: gcc
Version: 4.6.3
Status: UNCONFIRMED
Severity: normal
Priority: P