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] New: Powerpc compiler generates insn not found for -m32 -mpowerpc64
Date: Mon, 05 Jan 2015 21:04:00 -0000 [thread overview]
Message-ID: <bug-64505-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64505
Bug ID: 64505
Summary: Powerpc compiler generates insn not found for -m32
-mpowerpc64
Product: gcc
Version: 5.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: meissner at gcc dot gnu.org
Reporter: meissner at gcc dot gnu.org
Host: powerpc64-unknown-linux-gnu
Target: powerpc64-unknown-linux-gnu
Build: powerpc64-unknown-linux-gnu
Created attachment 34384
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=34384&action=edit
File that shows the problem
Compiling the attached file will generate an insn not found error message if it
is compiled with the following options: -std=c99 -fno-strict-aliasing -Wall
-m32 -mpowerpc64 foo.c -S -O2.
The problem is inside of rs6000_secondary_reload, there is code for 64-bit and
32-bit. The reload insn that is returned is looking for a 64-bit scratch
register, but the combination of switches -m32 -mpowerpc64 it should be
generating a 32-bit scratch register.
next reply other threads:[~2015-01-05 21:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-05 21:04 meissner at gcc dot gnu.org [this message]
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
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@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).