public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "meissner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/64505] Powerpc compiler generates insn not found for -m32 -mpowerpc64 Date: Tue, 13 Jan 2015 17:48:00 -0000 [thread overview] Message-ID: <bug-64505-4-o5ZFylEu6p@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-64505-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64505 --- Comment #3 from Michael Meissner <meissner at gcc dot gnu.org> --- Author: meissner Date: Tue Jan 13 17:47:29 2015 New Revision: 219547 URL: https://gcc.gnu.org/viewcvs?rev=219547&root=gcc&view=rev Log: 2015-01-12 Michael Meissner <meissner@linux.vnet.ibm.com> Backport from trunk 2015-01-06 Michael Meissner <meissner@linux.vnet.ibm.com> PR target/64505 * config/rs6000/rs6000.c (rs6000_secondary_reload): Return the correct reload handler if -m32 -mpowerpc64 is used. * testsuite/gcc.target/powerpc/pr64505.c: New file to test -m32 -mpowerpc64 fix is correct. Added: branches/ibm/gcc-4_8-branch/gcc/testsuite/gcc.target/powerpc/pr64505.c - copied unchanged from r219481, branches/gcc-4_9-branch/gcc/testsuite/gcc.target/powerpc/pr64505.c Modified: branches/ibm/gcc-4_8-branch/gcc/ChangeLog.ibm branches/ibm/gcc-4_8-branch/gcc/config/rs6000/rs6000.c
next prev parent reply other threads:[~2015-01-13 17:48 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-01-05 21:04 [Bug target/64505] New: " meissner at gcc dot gnu.org 2015-01-05 21:05 ` [Bug target/64505] " meissner at gcc dot gnu.org 2015-01-06 20:30 ` meissner at gcc dot gnu.org 2015-01-13 17:48 ` meissner at gcc dot gnu.org [this message] 2015-01-18 16:41 ` segher at gcc dot gnu.org 2015-01-27 21:45 ` bergner at gcc dot gnu.org 2015-01-27 21:47 ` bergner 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-64505-4-o5ZFylEu6p@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: 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).