From: Theo de Raadt <deraadt@cvs.openbsd.org>
To: Gabriel Dos Reis <gdr@integrable-solutions.net>
Cc: Daniel Jacobowitz <drow@false.org>,
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:59:00 -0000 [thread overview]
Message-ID: <200403010359.i213xcqp005885@cvs.openbsd.org> (raw)
In-Reply-To: Your message of "01 Mar 2004 04:44:58 +0100." <m3ishpjkn9.fsf@uniton.integrable-solutions.net>
> (I assumed you're not suggesting they download the entire BSD
> kernel)
We don't believe it is restricted to just our kernel. And we've never
really talked about kernel compile speed, instead we measure "make
build" time, that meaning the compilation of the full system --
kernel, bootblocks, all the libraries, everything. It is a giant
source tree.
A 40% slowdown from just changing compilers ... how do you explain
that? I explain it by saying the compiler builds the entire system
40% slower.
More than that, we think everything compiles slower, on all
architectures. There is some variance; some systems slow down more
than others.
And thus far, there's been no real evidence contrary.
Perhaps the gcc people are sticking to microbenchmarks?
We don't know. But they keep asking for micro-test reports... Why
don't they compare themselves to see how much slower it is. For
the best impact, I recommend using a sparc64. But an i386 or powerpc
will show it too.
next prev parent reply other threads:[~2004-03-01 3:59 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
2004-03-01 3:55 ` Gabriel Dos Reis
2004-03-01 3:59 ` Theo de Raadt [this message]
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=200403010359.i213xcqp005885@cvs.openbsd.org \
--to=deraadt@cvs.openbsd.org \
--cc=drow@false.org \
--cc=espie@quatramaran.ens.fr \
--cc=gcc@gcc.gnu.org \
--cc=gdr@integrable-solutions.net \
--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).