From: Daniel Phillips <phillips@bonn-fries.net>
To: Luigi Genoni <kernel@Expansa.sns.it>,
Anton Altaparmakov <aia21@cam.ac.uk>
Cc: war <war@starband.net>, Roy Sigurd Karlsbakk <roy@karlsbakk.net>,
<linux-kernel@vger.kernel.org>
Subject: Re: Which gcc version?
Date: Sat, 24 Nov 2001 17:09:27 +0100 [thread overview]
Message-ID: <E167fN7-0002RA-00@starship.berlin> (raw)
In-Reply-To: <Pine.LNX.4.33.0111241659120.6855-100000@Expansa.sns.it>
In-Reply-To: <Pine.LNX.4.33.0111241659120.6855-100000@Expansa.sns.it>
On November 24, 2001 05:01 pm, Luigi Genoni wrote:
> On Fri, 23 Nov 2001, Anton Altaparmakov wrote:
> > At 18:30 23/11/01, Daniel Phillips wrote:
> > >On November 23, 2001 02:59 pm, Anton Altaparmakov wrote:
> > > > gcc-3x OTOH is not a good idea at the moment.
> > >
> > >Do you have any particular reason for saying that?
> >
> > I haven't done any measurements myself but from what I have read, gcc-3.x
> > produces significantly slower code than gcc-2.96. I know I should try
> > myself some time... but if that is indeed true that is a very good reason
> > to stick with gcc-2.96.
>
> I did some serious bench.
> On all my codes, using eavilly floating point computation, binaries
> built with gcc 3.0.2 are about 5% slower that the ones built with 2.95.3
> on athlon processor with athlon optimizzations.
> On the other side, on sparclinux, same codes compiled with gcc 3.0.2 are
> really faster, about 20%, that with 2.95.3
Interesting, but not as interesting as knowing what the results are for
non-fp code, since we are talking about kernel compilation.
--
Daniel
next prev parent reply other threads:[~2001-11-24 16:08 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-23 12:53 Roy Sigurd Karlsbakk
2001-11-23 12:57 ` Arjan van de Ven
2001-11-23 13:51 ` war
2001-11-23 19:43 ` J Sloan
2001-11-23 13:59 ` Anton Altaparmakov
2001-11-23 14:11 ` war
2001-11-23 15:14 ` Arjan van de Ven
2001-11-23 15:30 ` Gábor Lénárt
2001-11-23 15:34 ` Arjan van de Ven
2001-11-23 17:13 ` Re[2]: " Nerijus Baliunas
2001-11-23 19:50 ` J Sloan
2001-11-23 20:34 ` John Jasen
2001-11-23 21:55 ` J Sloan
2001-11-24 3:08 ` John Jasen
2001-11-24 12:24 ` Paul G. Allen
2001-11-26 18:31 ` Alan Cox
2001-11-27 8:42 ` Ahmed Masud
2001-11-23 16:10 ` Anton Altaparmakov
2001-11-23 14:43 ` Anton Altaparmakov
2001-11-23 16:23 ` Jeff Garzik
2001-11-23 18:30 ` Daniel Phillips
2001-11-23 18:56 ` Anton Altaparmakov
2001-11-23 19:28 ` Daniel Phillips
2001-11-23 20:14 ` Andrew Morton
2001-11-23 20:24 ` Anton Altaparmakov
2001-11-23 20:35 ` Andrew Morton
2001-11-23 21:09 ` David Weinehall
2001-11-24 16:01 ` Luigi Genoni
2001-11-24 16:09 ` Daniel Phillips [this message]
2001-11-24 17:32 ` Luigi Genoni
-- strict thread matches above, loose matches on Subject: below --
2001-11-23 17:12 RaúlNúñez de Arenas Coronado
2001-11-23 18:02 ` M. Edward (Ed) Borasky
2001-11-23 18:14 ` Thorsten Glaser
2001-04-05 10:56 which " Manoj Sontakke
2001-04-05 5:48 ` Alexander Viro
2001-04-05 14:09 ` Manoj Sontakke
2001-04-05 11:37 ` Bart Trojanowski
2001-04-05 12:02 ` Matti Aarnio
2001-04-05 12:26 ` David Woodhouse
2001-04-05 12:31 ` Matti Aarnio
2001-04-05 13:09 ` Richard B. Johnson
2001-04-05 11:45 ` Matti Aarnio
2001-04-05 11:50 ` christophe barbe
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=E167fN7-0002RA-00@starship.berlin \
--to=phillips@bonn-fries.net \
--cc=aia21@cam.ac.uk \
--cc=kernel@Expansa.sns.it \
--cc=linux-kernel@vger.kernel.org \
--cc=roy@karlsbakk.net \
--cc=war@starband.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
all inboxes | Powered by JetHome®