public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "meissner at linux dot vnet.ibm.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/57386] ICE: hash-long-double-tr1-aux.cc:54:7: error: unrecognizable insn
Date: Thu, 12 Dec 2013 21:03:00 -0000 [thread overview]
Message-ID: <bug-57386-4-RF5h6n9VgU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-57386-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57386
--- Comment #12 from Michael Meissner <meissner at linux dot vnet.ibm.com> ---
On Thu, Dec 12, 2013 at 12:22:13AM +0000, meissner at linux dot vnet.ibm.com
wrote:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57386
>
> --- Comment #9 from Michael Meissner <meissner at linux dot vnet.ibm.com> ---
> On Wed, Dec 11, 2013 at 04:37:20PM +0000, dje at gcc dot gnu.org wrote:
> > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57386
> >
> > --- Comment #8 from David Edelsohn <dje at gcc dot gnu.org> ---
> > Mike, can you apply the patch to the 4.8 branch?
> >
> > Thanks, David
>
> Note, the patch no longer applies to the trunk due to adding a PTImode case.
> I'll test both gcc 4.8/trunk with the patch for both.
>
> Sorry for breaking this, and went unresponsive.
I tested this patch lifted from the bugzilla, and it does fix the problem for
GCC 4.8. I'm also including the appropriate patch for GCC 4.9 (different due
to the surrounding code being different). While there are other problems with
SPE in GCC 4.9, I feel this patch is safe to apply.
I have bootstraped the patch on a power7 running linux powerpc64 and there were
no regressions between the unpatched gcc 4.8 and the build with the patch
attached.
I have verified that the bug is fixed when I build a SPE compiler with the
patch attached for the GCC 4.8 patch.
I have also bootstraped the GCC 4.9 patch on a power7 running linux powerpc64.
As I write this message, I haven't done the make check regression test, but I
will do that shortly.
Are these patches ok to apply? I can apply just the 4.8 patch or both the 4.8
and 4.9 patches.
2013-12-12 Roland Stigge <stigge@antcom.de>
Michael Meissner <meissner@linux.vnet.ibm.com>
* config/rs6000/rs6000.c (rs6000_legitimate_offset_address_p):
Only check TFmode for SPE constants. Don't check TImode or
TDmode.
next prev parent reply other threads:[~2013-12-12 21:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-23 13:24 [Bug libstdc++/57386] New: " stigge at antcom dot de
2013-05-23 14:25 ` [Bug libstdc++/57386] " rguenth at gcc dot gnu.org
2013-05-24 11:18 ` stigge at antcom dot de
2013-05-24 11:49 ` paolo.carlini at oracle dot com
2013-05-24 15:23 ` stigge at antcom dot de
2013-12-01 11:53 ` [Bug target/57386] " stigge at antcom dot de
2013-12-11 12:49 ` stigge at antcom dot de
2013-12-11 12:51 ` stigge at antcom dot de
2013-12-12 0:22 ` meissner at linux dot vnet.ibm.com
2013-12-12 17:10 ` meissner at linux dot vnet.ibm.com
2013-12-12 21:03 ` meissner at linux dot vnet.ibm.com
2013-12-12 21:03 ` meissner at linux dot vnet.ibm.com [this message]
2013-12-12 23:42 ` stigge at antcom dot de
2014-01-07 19:57 ` meissner at gcc dot gnu.org
2014-01-07 20:10 ` meissner 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-57386-4-RF5h6n9VgU@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).