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: Wed, 12 Mar 2003 19:26:00 -0000 [thread overview] Message-ID: <20030312192600.31780.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 Cc: Subject: Re: optimization/2001: [3.2/3.3 regression] Inordinately long compile times in reload CSE regs Date: Wed, 12 Mar 2003 20:19:45 +0100 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=2001 Brad Lucier wrote: > Perhaps you were testing 3.4, where this is fixed? Or perhaps it requires > a large number of registers before gcc screws up. Here are the times I > now get, first for the 3.3 branch, then for 3.4: Uhm, yes I used 3.4. I got so many gcc versions around now, picked the wrong one. For 3.3, I get: at -O0: TOTAL : 4.66 0.24 6.14 at -O2: TOTAL : 316.67 1.71 329.12 Ouch. > The patch that fixed this for 3.4 was > > http://gcc.gnu.org/ml/gcc-cvs/2003-02/msg00742.html > > Perhaps it's in the RedHat 3.2 branch, too. Is that a combination of these two patches? http://gcc.gnu.org./ml/gcc-patches/2003-02/msg00858.html http://gcc.gnu.org./ml/gcc-patches/2003-02/msg01254.html rth mentioned 3 patches, but I can only find these two, and one other of which you said it did not apply to your sources. Any clue why this wasn't backported to 3.3? Greetz Steven
next reply other threads:[~2003-03-12 19:26 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-03-12 19:26 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-16 10:06 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=20030312192600.31780.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: linkBe 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).