All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Kirby <sim@netnation.com>
To: linux-kernel@vger.kernel.org
Subject: Re: gcc-2.95.3 vs gcc-3.0.4
Date: Mon, 25 Feb 2002 00:07:42 -0800	[thread overview]
Message-ID: <20020225080742.GA3122@netnation.com> (raw)
In-Reply-To: <3C771D29.942A07C2@starband.net> <20020222204456.O11156@work.bitmover.com> <3C77270A.1CBA02E8@zip.com.au>
In-Reply-To: <3C77270A.1CBA02E8@zip.com.au>

On Fri, Feb 22, 2002 at 09:22:18PM -0800, Andrew Morton wrote:

> Larry McVoy wrote:
> > 
> > Try 2.72, it's almost twice as fast as 2.95 for builds.  For BK, at least,
> > we don't see any benefit from the slower compiler, the code runs the same
> > either way.
> > 
> 
> Amen.
> 
> I want 2.7.2.3 back, but it was the name:value struct initialiser
> bug which killed that off.  2.91.66 isn't much slower than 2.7.x,
> and it's what I use.
> 
> "almost twice as fast"?  That means that 2.7.2 vs 3.x is getting
> up to a 3x difference.  Does anyone know why?

Me too.  Everybody says "it's the final code that matters", but a lot of
us would be more productive if the thing would just compile faster.  I've
done the same (used 2723 during development/debugging) and it helped
quite a lot.

I remember Borland Turbo Pascal's compiler... Yes, yes, but that thing
compiled insane amounts of code in split seconds on 386 hardware.

Simon-

[  Stormix Technologies Inc.  ][  NetNation Communications Inc. ]
[       sim@stormix.com       ][       sim@netnation.com        ]
[ Opinions expressed are not necessarily those of my employers. ]

  parent reply	other threads:[~2002-02-25  8:08 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-23  4:40 gcc-2.95.3 vs gcc-3.0.4 Justin Piszcz
2002-02-23  4:44 ` Larry McVoy
2002-02-23  5:13   ` Justin Piszcz
2002-02-23  5:22   ` Andrew Morton
2002-02-23  5:50     ` Richard Gooch
2002-02-23 10:31     ` Benny Sjostrand
2002-02-23 15:00     ` Martin Dalecki
2002-02-25  8:07     ` Simon Kirby [this message]
2002-02-25  8:15       ` David S. Miller
2002-02-25  8:32       ` David Rees
2002-02-25  9:32         ` Ian Castle
2002-02-25  9:52       ` Markus Schaber
2002-02-23  5:40 ` hugang
2002-02-23  5:56   ` Andrew Morton
2002-02-23  9:25     ` Paul G. Allen
2002-02-23 13:55       ` gmack
2002-02-23 15:43       ` bert hubert
2002-02-25  0:07       ` Luigi Genoni
2002-02-25  0:32         ` ANN: syscalltrack v0.7 released guy keren
2002-02-25  7:48         ` gcc-2.95.3 vs gcc-3.0.4 Jakub Jelinek
2002-02-25  9:46           ` Luigi Genoni
2002-02-25  9:59             ` Jakub Jelinek
2002-02-25 12:55               ` Jan Hubicka
2002-02-25 16:08 ` Juan Quintela

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=20020225080742.GA3122@netnation.com \
    --to=sim@netnation.com \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.