From: Theo de Raadt <deraadt@cvs.openbsd.org>
To: Eric Christopher <echristo@redhat.com>
Cc: Zack Weinberg <zack@codesourcery.com>,
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 04:05:00 -0000 [thread overview]
Message-ID: <200403010405.i2145YgI006299@cvs.openbsd.org> (raw)
In-Reply-To: Your message of "Sun, 29 Feb 2004 20:00:40 PST." <1078113640.4272.19.camel@dzur.sfbay.redhat.com>
> Sure, as long as you do timing tests and put it in bugzilla when you do
> it. If you can narrow down classes of slow testcases then you'll be
> helping as opposed to adding to the noise which you are currently doing.
Eric,
On the box where you are right now, what is the speed difference
between gcc2 compiling your kernel, versus gcc3 compiling your kernel.
Since I can bet gcc3 is slower for you, have you submitted detailed
test results for that?
Frankly, as consumers of your compiler we don't have a clue how to
start submitting results like you are suggesting we do. Clearly it is
not about test cases when we can't find anything faster!
We just see one point of analysis: This new compiler is even more of a
slug than the previous one.
But if you want, keep on ignoring what we point out... I'm sure Redhat
keeps buying you faster machines...
next prev parent reply other threads:[~2004-03-01 4:05 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
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 ` Gabriel Dos Reis
2004-03-01 4:00 ` Eric Christopher
2004-03-01 4:05 ` Theo de Raadt [this message]
2004-03-01 4:11 ` Eric Christopher
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=200403010405.i2145YgI006299@cvs.openbsd.org \
--to=deraadt@cvs.openbsd.org \
--cc=echristo@redhat.com \
--cc=espie@quatramaran.ens.fr \
--cc=gcc@gcc.gnu.org \
--cc=pinskia@physics.uc.edu \
--cc=tech@openbsd.org \
--cc=zack@codesourcery.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 read-only IMAP folder(s) and NNTP newsgroup(s).