public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: dewar@gnat.com (Robert Dewar)
To: dnovillo@redhat.com, neil@daikokuya.co.uk
Cc: gcc@gcc.gnu.org
Subject: Re: Bootstrap times on mainline are getting worse
Date: Thu, 17 Oct 2002 17:10:00 -0000	[thread overview]
Message-ID: <20021017215540.D95F5F2D4A@nile.gnat.com> (raw)

>>This is truly depressing.  There seems to be nothing we can do
to prevent it.

At the very least,we could measure the bootstrap performance impact of
each patch.

I must say the cumulative difference is quite noticeable. I am switching
from using OS/2, GCC 2.8.1 on a 300MHz P3, to XP, GCC 3.2, 1.3 GHz P3,
and the compilation time is about the same, yes there are other variables
(OS/2 is definitely a lot more efficient than XP), but still a significant
difference.

             reply	other threads:[~2002-10-17 21:55 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-17 17:10 Robert Dewar [this message]
2002-10-17 17:26 ` Diego Novillo
  -- strict thread matches above, loose matches on Subject: below --
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
2002-10-19 13:51 Roger Sayle
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
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

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=20021017215540.D95F5F2D4A@nile.gnat.com \
    --to=dewar@gnat.com \
    --cc=dnovillo@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=neil@daikokuya.co.uk \
    /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).