public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pthaugen at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/47862] Incorrect code for spilling a vector register
Date: Mon, 07 Mar 2011 19:40:00 -0000	[thread overview]
Message-ID: <bug-47862-4-nIUfJWRh6L@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47862-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Pat Haugen <pthaugen at gcc dot gnu.org> 2011-03-07 19:40:21 UTC ---
Author: pthaugen
Date: Mon Mar  7 19:40:15 2011
New Revision: 170749

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=170749
Log:
        PR target/47862
        * config/rs6000/rs6000.h (HARD_REGNO_CALLER_SAVE_MODE): Define.

        * gcc.target/powerpc/pr47862.c: New.


Added:
    branches/gcc-4_5-branch/gcc/testsuite/gcc.target/powerpc/pr47862.c
Modified:
    branches/gcc-4_5-branch/gcc/ChangeLog
    branches/gcc-4_5-branch/gcc/config/rs6000/rs6000.h
    branches/gcc-4_5-branch/gcc/testsuite/ChangeLog


  parent reply	other threads:[~2011-03-07 19:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-23 18:06 [Bug rtl-optimization/47862] New: " pthaugen at gcc dot gnu.org
2011-02-24 22:00 ` [Bug rtl-optimization/47862] " pthaugen at gcc dot gnu.org
2011-02-25  1:43 ` pthaugen at gcc dot gnu.org
2011-02-25 17:52 ` pthaugen at gcc dot gnu.org
2011-03-04 21:37 ` bergner at gcc dot gnu.org
2011-03-07 19:27 ` pthaugen at gcc dot gnu.org
2011-03-07 19:40 ` pthaugen at gcc dot gnu.org [this message]
2011-03-07 19:47 ` pthaugen at gcc dot gnu.org
2011-03-07 20:06 ` pthaugen at gcc dot gnu.org
2011-03-15 19:59 ` pthaugen at gcc dot gnu.org
2011-03-16 20:22 ` pthaugen at gcc dot gnu.org

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=bug-47862-4-nIUfJWRh6L@http.gcc.gnu.org/bugzilla/ \
    --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).