From: Diego Novillo <dnovillo@redhat.com>
To: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>
Cc: ritzert@t-online.de, schwab@suse.de, gcc@gcc.gnu.org
Subject: Re: Bootstrap times on mainline are getting worse
Date: Fri, 18 Oct 2002 05:42:00 -0000 [thread overview]
Message-ID: <20021018112206.GA22977@tornado.toronto.redhat.com> (raw)
In-Reply-To: <200210180359.XAA24196@caip.rutgers.edu>
On Thu, 17 Oct 2002, Kaveh R. Ghazi wrote:
> That would be a proper "apples to apples" comparison upon which you
> could draw conclusions about whether compile-time speed was slowing
> down. I'm not saying it isn't slowing down, but that the figures
> posted so far aren't actually measuring that AFAICT.
>
Very good point. I should've thought of that before. We could
analyze SPEC build times instead.
http://people.redhat.com/dnovillo/spec95/gcc/global-build-secs_elapsed.html
For CINT95 base, we have a 6% increase in build times since
Sep19. There is a noticeable jump around Oct06.
Diego.
next prev parent reply other threads:[~2002-10-18 11:22 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
2002-10-18 4:34 ` Michael Ritzert
2002-10-18 4:52 ` Kaveh R. Ghazi
2002-10-18 5:42 ` Diego Novillo [this message]
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=20021018112206.GA22977@tornado.toronto.redhat.com \
--to=dnovillo@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=ghazi@caip.rutgers.edu \
--cc=ritzert@t-online.de \
--cc=schwab@suse.de \
/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).