From: prj@po.cwru.edu (Paul Jarc)
To: gcc@gcc.gnu.org
Subject: Re: GCC still getting a lot slower
Date: Tue, 31 Dec 2002 16:53:00 -0000 [thread overview]
Message-ID: <m38yy5rgr4.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <20021231215422.GA2032@doctormoo> (Nathanael Nerode's message of "Tue, 31 Dec 2002 16:54:22 -0500")
Nathanael Nerode <neroden@twcny.rr.com> wrote:
> Paul Jarc said:
>> Nathanael Nerode <neroden@twcny.rr.com> wrote:
>>> Frankly, I don't think we should look at bootstrap time. A number of
>>> the largest changes in B-I-B were necessary build process changes, which
>>> are quite likely to slow down the build *of* the compiler, but not the
>>> performance of the compiler. Or, in other words, "so what?". ;-)
>>
>> As someone else noted a while ago, bootstrap times are important
>> because changes are tested by bootstrapping. So slow bootstraps slow
>> down all other progress.
>
> Yeah. But when I said 'necessary', I meant it; these changes have been
> on the TODO list forever, and they're correctness issues.
I wasn't disputing that - just pointing out that bootstrap times are
indeed important, in answer to your "so what".
paul
next prev parent reply other threads:[~2002-12-31 22:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-31 16:14 Nathanael Nerode
2002-12-31 16:53 ` Paul Jarc [this message]
[not found] <1041382480.23232.35.camel@steven>
2003-01-02 14:24 ` Jan Hubicka
-- strict thread matches above, loose matches on Subject: below --
2002-12-31 23:01 Ritzert
2002-12-31 14:11 Nathanael Nerode
2002-12-31 14:49 ` Paul Jarc
2002-12-31 17:16 ` Diego Novillo
2003-01-02 10:59 ` Gerald Pfeifer
2003-01-02 14:21 ` Jan Hubicka
2003-01-03 0:21 ` Fergus Henderson
2003-01-03 14:05 ` Jan Hubicka
2003-01-03 10:33 ` Ben Elliston
2002-12-31 13:44 Neil Booth
2002-12-31 13:47 ` Paolo Carlini
2002-12-31 13:48 ` Neil Booth
2002-12-31 13:55 ` Paolo Carlini
2002-12-31 14:00 ` Neil Booth
2002-12-31 20:22 ` David Edelsohn
2002-12-31 14:00 ` Diego Novillo
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=m38yy5rgr4.fsf@multivac.cwru.edu \
--to=prj@po.cwru.edu \
--cc=gcc@gcc.gnu.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).