From: Thilo Bangert <thilo.bangert@gmx.net>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] GCC 3 Vs GCC 2 and some other stuff
Date: Mon, 8 Apr 2002 18:46:02 +0200 [thread overview]
Message-ID: <20020408171720.64E9A20AADCC@chiba.3jane.net> (raw)
In-Reply-To: <200204081154.02951.verwilst@gentoo.org>
On Monday, 8. April 2002 11:54, you wrote:
> Hi
>
> Euhm...
> These benchmarks of spider were compile times? :o)
> Damn.. I still don't know wether i will have a faster system with gcc
> 3.x than i had with gcc 2.95.x... please tell me:
> Is gcc 3.x faster than 2.95 during RUNTIME and execution of the
> program?
the german magazin ix ( http://www.heise.de/ix/ ) did some benchmarks
(spec) on gcc 3.0 and gcc 2.95.3 which showed that gcc3.0 was faster -
but not by much
in some cases (bzip) it was slower!
but then, i don't remember if they bootstrapped the compiler....
>
> Thanks! :o)
--
regards
Thilo
prev parent reply other threads:[~2002-04-08 17:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-08 1:39 [gentoo-dev] GCC 3 Vs GCC 2 and some other stuff Eugenia Loli-Queru
2002-04-08 2:46 ` Spider
2002-04-08 5:00 ` Stacey Keast
2002-04-08 6:18 ` Spider
2002-04-08 5:33 ` Geert Bevin
2002-04-08 19:49 ` Spider
2002-04-08 9:54 ` Bart Verwilst
2002-04-08 9:57 ` Einar Karttunen
2002-04-08 16:46 ` Thilo Bangert [this message]
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=20020408171720.64E9A20AADCC@chiba.3jane.net \
--to=thilo.bangert@gmx.net \
--cc=gentoo-dev@gentoo.org \
/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