linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Bradford <john@grabjohn.com>
To: akpm@digeo.com, lm@bitmover.com
Cc: acme@conectiva.com.br, alan@lxorguk.ukuu.org.uk, cw@f00f.org,
	geert@linux-m68k.org, linux-kernel@vger.kernel.org,
	perex@suse.cz, phillips@arcor.de, torvalds@transmeta.com
Subject: Re: GCC speed (was [PATCH] Isapnp warning)
Date: Mon, 23 Jun 2003 08:40:52 +0100	[thread overview]
Message-ID: <200306230740.h5N7eqUN000268@81-2-122-30.bradfords.org.uk> (raw)

> If you think 3.[23] are slow, go back and compile with 2.7.2 - it's much
> faster than the later versions.  I used to yank newer versions of gcc
> off systems and put 2.7.2 on, I think it was close to 2x faster at
> compilation and made no difference on BK performance.

Out of interest, have you tried compiling BK with tcc?

John.

             reply	other threads:[~2003-06-23  7:19 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-23  7:40 John Bradford [this message]
2003-06-23 13:17 ` GCC speed (was [PATCH] Isapnp warning) Larry McVoy
  -- strict thread matches above, loose matches on Subject: below --
2003-06-22 20:07 John Bradford
2003-06-22 20:27 ` Michael Buesch
2003-06-22 19:03 John Bradford
2003-06-21 19:51 [PATCH] Isapnp warning Andrew Morton
2003-06-22  1:43 ` Arnaldo Carvalho de Melo
2003-06-22  2:17   ` Andrew Morton
2003-06-22 13:22     ` GCC speed (was [PATCH] Isapnp warning) Daniel Phillips
2003-06-22 17:32       ` Andrew Morton
2003-06-22 17:56         ` Linus Torvalds
2003-06-22 18:58         ` Henning P. Schmiedehausen
2003-06-22 19:12           ` Sam Ravnborg
2003-06-22 19:13           ` Andrew Morton
2003-06-22 19:32             ` Henning Schmiedehausen
2003-06-22 19:51           ` Adrian Bunk
2003-06-22 19:12         ` Daniel Phillips
2003-06-23  1:05         ` Larry McVoy
2002-01-04 11:32           ` Pavel Machek
2003-07-17 10:18             ` Christoph Hellwig
2003-07-17 10:23               ` Jakub Jelinek
2003-07-17 10:27                 ` Christoph Hellwig

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=200306230740.h5N7eqUN000268@81-2-122-30.bradfords.org.uk \
    --to=john@grabjohn.com \
    --cc=acme@conectiva.com.br \
    --cc=akpm@digeo.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=cw@f00f.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm@bitmover.com \
    --cc=perex@suse.cz \
    --cc=phillips@arcor.de \
    --cc=torvalds@transmeta.com \
    /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;
as well as URLs for NNTP newsgroup(s).