public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/37490] [4.4/4.5 Regression] IRA causes FP code to have more spills
Date: Thu, 25 Feb 2010 18:56:00 -0000	[thread overview]
Message-ID: <20100225185541.13650.qmail@sourceware.org> (raw)
In-Reply-To: <bug-37490-6528@http.gcc.gnu.org/bugzilla/>



------- Comment #7 from law at redhat dot com  2010-02-25 18:55 -------
I'm not a PPC expert, but the code looks pretty good at this point.    I'd have
to assume Vlad's patch for 37488 and possibly other follow-on work resulted in
the improvements.  I'm closing this PR as resolved.  If you feel it should be
kept open, feel free to re-open it.


-- 

law at redhat dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |FIXED


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37490


      parent reply	other threads:[~2010-02-25 18:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-11 23:46 [Bug rtl-optimization/37490] New: [4.4 " pinskia at gcc dot gnu dot org
2008-09-11 23:46 ` [Bug rtl-optimization/37490] " pinskia at gcc dot gnu dot org
2008-09-11 23:49 ` pinskia at gcc dot gnu dot org
2008-09-11 23:55 ` pinskia at gcc dot gnu dot org
2008-09-13 12:43 ` rguenth at gcc dot gnu dot org
2008-10-22  3:11 ` mmitchel at gcc dot gnu dot org
2008-12-24 23:03 ` pinskia at gcc dot gnu dot org
2009-02-16  9:12 ` bonzini at gnu dot org
2009-02-17 20:48 ` pinskia at gcc dot gnu dot org
2009-04-21 15:59 ` [Bug rtl-optimization/37490] [4.4/4.5 " jakub at gcc dot gnu dot org
2009-07-22 10:35 ` jakub at gcc dot gnu dot org
2009-10-15 12:54 ` jakub at gcc dot gnu dot org
2010-01-21 13:15 ` jakub at gcc dot gnu dot org
2010-02-25 18:56 ` law at redhat dot com [this message]

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=20100225185541.13650.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).