From: Con Kolivas <conman@kolivas.net>
To: Robert Love <rml@tech9.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BENCHMARK] gcc3.2 v 2.95.3 (contest and linux-2.5.38)
Date: Mon, 23 Sep 2002 13:16:58 +1000 [thread overview]
Message-ID: <1032751018.3d8e87aa99cc2@kolivas.net> (raw)
In-Reply-To: <1032750631.966.1003.camel@phantasy>
Quoting Robert Love <rml@tech9.net>:
> On Sun, 2002-09-22 at 23:04, Con Kolivas wrote:
>
> > IO Full Load:
> > Kernel Time CPU
> > 2.5.38 170.21 42%
> > 2.5.38-gcc32 1405.25 8%
>
> Ugh?? Something is _seriously_ messed up here.
Agreed!
> The CPU utilization is only 8% but the time is nearly 10x worse. You
> sure the only difference was the compiler? I could think gcc-3.2 makes
> some poorer choices wrt code optimization, but nothing feasible can come
> to mind that would produce such terrible results.
Absolutely certain. I'm shaking from the results still... hard to type...
> Also, I believe RedHat is compiling their kernel in 8.0 with gcc-3.2,
> unless they reintroduced kgcc. Surely that are not seeing these abysmal
> numbers.
contest is a new benchmark. Noone has ever done anything like this before so it
wouldn't have shown up in ordinary benchmarks. Mandrake has done the same with
LM9.0 I believe
Con
next prev parent reply other threads:[~2002-09-23 3:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-23 3:04 [BENCHMARK] gcc3.2 v 2.95.3 (contest and linux-2.5.38) Con Kolivas
2002-09-23 3:10 ` Robert Love
2002-09-23 3:16 ` Con Kolivas [this message]
2002-09-23 11:06 ` Mark Veltzer
2002-09-23 13:56 ` Daniel Jacobowitz
2002-09-23 3:28 ` Robert Love
2002-09-23 3:41 ` Andrew Morton
2002-09-23 3:46 ` Daniel Jacobowitz
2002-09-23 3:50 ` Con Kolivas
[not found] ` <3D8E9158.4E3DE029@digeo.com>
[not found] ` <1032754853.3d8e96a520836@kolivas.net>
[not found] ` <3D8E988F.DCB3196D@digeo.com>
2002-09-23 5:13 ` Con Kolivas
2002-09-23 7:20 ` Axel H. Siebenwirth
2002-09-23 3:47 ` Robert Love
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1032751018.3d8e87aa99cc2@kolivas.net \
--to=conman@kolivas.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@tech9.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox