public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/56548] [4.8 Regression] ICE in emit_move_insn, at expr.c:3486 with -march=pentium{pro,2,3} -O3
Date: Wed, 06 Mar 2013 10:23:00 -0000 [thread overview]
Message-ID: <bug-56548-4-SkYmpYkdhA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56548-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56548
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
AssignedTo|unassigned at gcc dot |jakub at gcc dot gnu.org
|gnu.org |
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> 2013-03-06 10:22:44 UTC ---
Created attachment 29595
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=29595
gcc48-pr56548.patch
Untested fix. Note I have no idea what performance issue on MIPS the patch
that regressed this was fixing and whether this fix doesn't undo that (or parts
thereof). On the other side, unexpectedly returning a rtx in different mode
from what has been requested is a sure way to ICEs or miscompilations.
next prev parent reply other threads:[~2013-03-06 10:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-06 9:01 [Bug middle-end/56548] New: " d.g.gorbachev at gmail dot com
2013-03-06 9:58 ` [Bug middle-end/56548] " jakub at gcc dot gnu.org
2013-03-06 10:23 ` jakub at gcc dot gnu.org [this message]
2013-03-06 17:20 ` jakub at gcc dot gnu.org
2013-03-06 17:24 ` jakub at gcc dot gnu.org
2013-03-06 18:06 ` sje at gcc dot gnu.org
2013-03-06 18:20 ` jakub at gcc dot gnu.org
2013-03-06 18:24 ` sje at gcc dot gnu.org
2013-05-16 12:33 ` ralf@linux-mips.org
2013-05-16 14:35 ` ralf@linux-mips.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-56548-4-SkYmpYkdhA@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).