[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0701031804320.8503@Phoenix.oltrelinux.com>
Date: Wed, 3 Jan 2007 18:06:09 +0100 (CET)
From: l.genoni@...relinux.com
To: Linus Torvalds <torvalds@...l.org>
cc: Grzegorz Kulewski <kangur@...com.net>,
Alan <alan@...rguk.ukuu.org.uk>,
Mikael Pettersson <mikpe@...uu.se>, s0348365@....ed.ac.uk,
76306.1226@...puserve.com, akpm@...l.org, bunk@...sta.de,
greg@...ah.com, linux-kernel@...r.kernel.org,
yanmin_zhang@...ux.intel.com
Subject: Re: kernel + gcc 4.1 = several problems
Just to make clearer why I am so curious, this from X86_64 X2 3800+:
DarkStar:{venom}:/tmp> gcc -DCMOV -Wall -O2 t.c
DarkStar:{venom}:/tmp>time ./a.out
600000000
real 0m0.151s
user 0m0.150s
sys 0m0.000s
DarkStar:{venom}:/tmp> gcc -Wall -O2 t.c
DarkStar:{venom}:/tmp> time ./a.out
600000000
real 0m0.176s
user 0m0.180s
sys 0m0.000s
DarkStar:{venom}:/tmp>gcc -m32 -DCMOV -Wall -O2 t.c
DarkStar:{venom}:/tmp>time ./a.out
600000000
real 0m0.152s
user 0m0.160s
sys 0m0.000s
DarkStar:{venom}:/tmp>gcc -m32 -Wall -O2 t.c
DarkStar:{venom}:/tmp>time ./a.out
600000000
real 0m0.200s
user 0m0.200s
sys 0m0.000s
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists