From: Theo de Raadt <deraadt@cvs.openbsd.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: Andrew Pinski <pinskia@physics.uc.edu>,
tech@openbsd.org, Marc Espie <espie@quatramaran.ens.fr>,
"gcc@gcc.gnu.org List" <gcc@gcc.gnu.org>
Subject: Re: gcc and compiling speed
Date: Mon, 01 Mar 2004 03:46:00 -0000 [thread overview]
Message-ID: <200403010346.i213ku02017230@cvs.openbsd.org> (raw)
In-Reply-To: Your message of "Sun, 29 Feb 2004 22:07:09 EST." <20040301030709.GA28440@nevyn.them.org>
> > > Marc,
> > > Now I know you have been asked before every time you bring up on the
> > > GCC's mailing list about a set of preprocessed source for openbsd so
> > > that the speed of GCC will improve.
> >
> > How will this improve the speed of gcc?
> >
> > Are pre-processed headers the way that gcc3 is going to recover
> > the speed that it has lost?
>
> I found pretty Andrew's request very confusingly worded (sorry
> Andrew!), so let me rephrase it: preprocessed (-E, -save-temps) output
> for specific test cases that have slowed down. This is what people ask
> Marc for every time he reports slowdown numbers, and so far he hasn't
> provided any.
Is include file parsing a time critical component of gcc?
Is it a part that has slowed down a lot?
Quite frankly, I bet that cpp performance is entirely lost in the
noise...
> Not that we're disputing that GCC has slowed down. But without
> specific testcases that have regressed, it's hard to do anything about
> it.
Please.... an entire operating system compiles slower, on every
architecture we have tested it, and I have not heard of any case which
compiles faster (except sha1.c on sparc cpus, where gcc got into some
optimizer loop).
next prev parent reply other threads:[~2004-03-01 3:46 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-01 0:43 Andrew Pinski
2004-03-01 2:58 ` Theo de Raadt
2004-03-01 3:07 ` Daniel Jacobowitz
2004-03-01 3:46 ` Theo de Raadt [this message]
2004-03-01 3:55 ` Gabriel Dos Reis
2004-03-01 3:59 ` Theo de Raadt
2004-03-01 4:15 ` Daniel Berlin
2004-03-14 22:15 ` Gerald Pfeifer
2004-03-01 6:00 ` Andreas Jaeger
2004-03-01 19:40 ` Peter Galbavy
2004-03-01 19:51 ` Andreas Jaeger
2004-03-01 20:05 ` Peter Galbavy
2004-03-01 20:15 ` William Ahern
2004-03-01 3:10 ` Zack Weinberg
2004-03-01 3:49 ` Theo de Raadt
2004-03-01 4:00 ` Eric Christopher
2004-03-01 4:05 ` Theo de Raadt
2004-03-01 4:11 ` Eric Christopher
2004-03-01 4:00 ` Gabriel Dos Reis
2004-03-01 4:01 ` Zack Weinberg
[not found] ` <20040301071403.GA8953@tetto.gentiane.org>
2004-03-01 7:27 ` Zack Weinberg
2004-03-01 8:09 ` Steven Bosscher
2004-03-01 4:23 Vincent Diepeveen
2004-03-01 5:00 ` John S. Dyson
2004-03-01 5:31 ` Zack Weinberg
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=200403010346.i213ku02017230@cvs.openbsd.org \
--to=deraadt@cvs.openbsd.org \
--cc=drow@false.org \
--cc=espie@quatramaran.ens.fr \
--cc=gcc@gcc.gnu.org \
--cc=pinskia@physics.uc.edu \
--cc=tech@openbsd.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).