im using gcc 3.2.3 and i was woundering if it was still going to brake every
thing if i use -march=pentium4?
--
[EMAIL PROTECTED] mailing list
Adam Dunstan wrote:
im using gcc 3.2.3 and i was woundering if it was still going to brake every
thing if i use -march=pentium4?
I use it, and i don't have any problem.
i have a celeron 2Ghz ( @ 2,7Ghz :-) )
my flags :
CFLAGS=-march=pentium4 -O2 -frename-registers -pipe -fomit-frame-pointer
On Wed, 2003-08-27 at 12:19, Nicolas STURMEL wrote:
Adam Dunstan wrote:
im using gcc 3.2.3 and i was woundering if it was still going to brake every
thing if i use -march=pentium4?
I use it, and i don't have any problem.
i have a celeron 2Ghz ( @ 2,7Ghz :-) )
my flags :
gabor wrote:
On Wed, 2003-08-27 at 12:19, Nicolas STURMEL wrote:
Adam Dunstan wrote:
im using gcc 3.2.3 and i was woundering if it was still going to brake every
thing if i use -march=pentium4?
I use it, and i don't have any problem.
i have a celeron 2Ghz ( @ 2,7Ghz :-) )
my flags :
On Wed, 2003-08-27 at 13:34, Nicolas STURMEL wrote:
gabor wrote:
On Wed, 2003-08-27 at 12:19, Nicolas STURMEL wrote:
Adam Dunstan wrote:
im using gcc 3.2.3 and i was woundering if it was still going to brake every
thing if i use -march=pentium4?
I use it, and i don't have any
gabor wrote:
start this:
python -c 'int(10.1); int(1.3); int(1.2)'
on a 'normal' computer, it ends without any output.
on the miscompiled pentium4 computers it ends with an overflow error.
so basically if it ends with overflow error, gcc broke python because of
the
