From: Larry McVoy <lm@bitmover.com>
To: Andrew Morton <akpm@digeo.com>
Cc: Daniel Phillips <phillips@arcor.de>,
acme@conectiva.com.br, cw@f00f.org, torvalds@transmeta.com,
geert@linux-m68k.org, alan@lxorguk.ukuu.org.uk, perex@suse.cz,
linux-kernel@vger.kernel.org
Subject: Re: GCC speed (was [PATCH] Isapnp warning)
Date: Sun, 22 Jun 2003 18:05:55 -0700 [thread overview]
Message-ID: <20030623010555.GA4302@work.bitmover.com> (raw)
In-Reply-To: <20030622103251.158691c3.akpm@digeo.com>
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.
On Sun, Jun 22, 2003 at 10:32:51AM -0700, Andrew Morton wrote:
> Daniel Phillips <phillips@arcor.de> wrote:
> >
> > As for compilation speed, yes, that sucks. I doubt there's any rational
> > reason for it, but I also agree with the idea that correctness and binary
> > code performance should come first, then the compilation speed issue should
> > be addressed.
>
> No. Compilation inefficiency directly harms programmer efficiency and the
> quality and volume of code the programmer produces. These are surely the
> most important things by which a toolchain's usefulness should be judged.
>
> I compile with -O1 all the time and couldn't care the teeniest little bit
> about the performance of the generated code - it just doesn't matter.
>
> I'm happy allowing those thousands of people who do not compile kernels all
> the time to shake out any 3.2/3.3 compilation problems.
>
>
> Compilation inefficiency is the most serious thing wrong with gcc.
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
next prev parent reply other threads:[~2003-06-23 0:52 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-15 18:36 [PATCH] Isapnp warning Geert Uytterhoeven
2003-06-21 12:31 ` Alan Cox
2003-06-21 14:59 ` Geert Uytterhoeven
2003-06-21 15:04 ` Sean Neakums
2003-06-21 19:51 ` Andrew Morton
2003-06-21 23:53 ` Linus Torvalds
2003-06-22 0:11 ` Arnaldo Carvalho de Melo
2003-06-22 1:41 ` Chris Wedgwood
2003-06-22 1:43 ` Arnaldo Carvalho de Melo
2003-06-22 2:17 ` Andrew Morton
2003-06-22 2:27 ` Chris Wedgwood
2003-06-22 2:59 ` Andrew Morton
2003-06-22 5:50 ` Herbert Xu
2003-06-22 3:43 ` Martin J. Bligh
2003-06-22 4:24 ` Paul Mackerras
2003-06-22 8:32 ` Geert Uytterhoeven
2003-06-22 13:34 ` Daniel Phillips
2003-06-22 5:39 ` gcc 3.3: largest *and* smallest kernels (was Re: [PATCH] Isapnp warning) Barry K. Nathan
2003-06-22 11:31 ` Alan Cox
2003-06-22 13:22 ` GCC speed (was " 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 [this message]
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
2003-06-22 8:49 ` [PATCH] Isapnp warning Russell King
2003-06-22 8:39 ` Jörn Engel
2003-06-22 14:07 ` Daniel Phillips
2003-06-22 15:00 ` Jan-Benedict Glaw
2003-06-22 19:03 GCC speed (was [PATCH] Isapnp warning) John Bradford
2003-06-22 20:07 John Bradford
2003-06-22 20:27 ` Michael Buesch
2003-06-23 7:40 John Bradford
2003-06-23 13:17 ` Larry McVoy
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=20030623010555.GA4302@work.bitmover.com \
--to=lm@bitmover.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=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).