From: Andreas Schwab <schwab@suse.de>
To: Diego Novillo <dnovillo@redhat.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Bootstrap times on mainline are getting worse
Date: Thu, 17 Oct 2002 13:02:00 -0000 [thread overview]
Message-ID: <jebs5tp11v.fsf@sykes.suse.de> (raw)
In-Reply-To: <20021017144047.GA13629@tornado.toronto.redhat.com> (Diego Novillo's message of "Thu, 17 Oct 2002 10:40:47 -0400")
Diego Novillo <dnovillo@redhat.com> writes:
|> http://people.redhat.com/dnovillo/spec95/gcc/gcc-stats.html
|>
|> Bootstrap times have been creeping up lately. Today's mainline
|> is 10% slower to bootstrap C and Fortran than a month ago.
|> The biggest increase in bootstrap times seems to have come after
|> Oct05.
Not so on ia64. In fact, bootstrap times have decreased here.
http://gcc.gnu.org/ml/gcc-testresults/2002-10/msg00043.html
http://gcc.gnu.org/ml/gcc-testresults/2002-10/msg00549.html
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2002-10-17 14:55 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-17 12:51 Diego Novillo
2002-10-17 13:02 ` Andreas Schwab [this message]
2002-10-18 4:34 ` Michael Ritzert
2002-10-18 4:52 ` Kaveh R. Ghazi
2002-10-18 5:42 ` Diego Novillo
2002-10-18 9:02 ` Kaveh R. Ghazi
2002-10-18 9:48 ` Diego Novillo
2002-10-18 12:34 ` David Edelsohn
2002-10-19 12:01 ` Pop Sébastian
2002-10-19 14:14 ` Zack Weinberg
2002-10-20 9:19 ` Pop Sébastian
2002-10-20 14:41 ` Pop Sébastian
2002-10-20 15:41 ` Pop Sébastian
2002-11-04 17:54 ` Pop Sébastian
2002-10-17 14:22 ` Neil Booth
2002-10-17 14:49 ` Diego Novillo
2002-10-17 17:10 Robert Dewar
2002-10-17 17:26 ` Diego Novillo
2002-10-19 13:51 Roger Sayle
2002-10-19 14:51 Roger Sayle
2002-10-19 17:26 ` Zack Weinberg
2002-10-20 1:23 ` Roger Sayle
2002-10-20 15:09 ` Zack Weinberg
2002-10-19 18:36 ` Geert Bosch
2002-10-20 5:46 ` Tim Prince
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=jebs5tp11v.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=dnovillo@redhat.com \
--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).