public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Steven Bosscher <s.bosscher@student.tudelft.nl>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: optimization/2001: [3.2/3.3 regression] Inordinately long compile times in reload CSE regs
Date: Sun, 16 Mar 2003 10:06:00 -0000	[thread overview]
Message-ID: <20030316100601.32336.qmail@sources.redhat.com> (raw)

The following reply was made to PR optimization/2001; it has been noted by GNATS.

From: Steven Bosscher <s.bosscher@student.tudelft.nl>
To: gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org,
	lucier@math.purdue.edu, nobody@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	rth@redhat.com
Cc:  
Subject: Re: optimization/2001: [3.2/3.3 regression] Inordinately long compile
 times in reload CSE regs
Date: Sun, 16 Mar 2003 11:03:09 +0100

 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=2001
 
 Richard's patch really improves things a lot for me:
 http://gcc.gnu.org/ml/gcc-patches/2003-03/msg01478.html
 
 If somebody tries this:  The patch doesn't apply cleanly, the
 first hunk of bb-reorder.c needs to be applied manually.
 
 The numbers:
 
 GCC 3.3, March 12 sources:
 
 at -O0:  TOTAL         :   4.66       0.24       6.14
 at -O2:  TOTAL         : 316.67       1.71     329.12
 
 GCC 3.3, March 16 sources + Richard's patch:
 
 at -O0:  TOTAL         :   3.17       0.15       3.50
 at -O2:  TOTAL         :   5.60       0.17       5.91
 
 The latter is the avarage of three runs because I could hardly
 believe these numbers.
 
 Brad, this is worth a try, don't you think?  :-)
 
 Greetz
 Steven
 
 


             reply	other threads:[~2003-03-16 10:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-16 10:06 Steven Bosscher [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-22 12:23 paolo
2003-03-21 23:26 Mark Mitchell
2003-03-21 23:06 Steven Bosscher
2003-03-12 19:26 Steven Bosscher
2003-03-11 23:56 Steven Bosscher

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=20030316100601.32336.qmail@sources.redhat.com \
    --to=s.bosscher@student.tudelft.nl \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).