public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kkojima at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/49305] SH Target: internal compiler error: in reload_cse_simplify_operands, at postreload.c:403
Date: Wed, 08 Jun 2011 14:03:00 -0000 [thread overview]
Message-ID: <bug-49305-4-phVgu1HDS9@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49305-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49305
--- Comment #3 from Kazumoto Kojima <kkojima at gcc dot gnu.org> 2011-06-08 14:03:02 UTC ---
It's my fault after all. The patch r174586 should check the mode
parameter too. Without checking mode, insn-recog routines are
confused and the combine pass makes insns with wrong insn_code.
Now I'm testing
--- ORIG/trunk/gcc/config/sh/predicates.md 2011-06-04 10:16:51.000000000
+0900
+++ trunk/gcc/config/sh/predicates.md 2011-06-08 18:55:09.000000000 +0900
@@ -395,6 +395,7 @@
}
if ((mode == QImode || mode == HImode)
+ && mode == GET_MODE (op)
&& (MEM_P (op)
|| (GET_CODE (op) == SUBREG && MEM_P (SUBREG_REG (op)))))
{
@@ -432,6 +433,7 @@
return 0;
if ((mode == QImode || mode == HImode)
+ && mode == GET_MODE (op)
&& (MEM_P (op)
|| (GET_CODE (op) == SUBREG && MEM_P (SUBREG_REG (op)))))
{
I'll apply it if it survives the tests on sh-elf and sh4-unknown-linux-gnu
and put the patch in #1 into my TODO list.
next prev parent reply other threads:[~2011-06-08 14:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-06 23:44 [Bug target/49305] New: " oleg.endo@t-online.de
2011-06-07 14:04 ` [Bug target/49305] " kkojima at gcc dot gnu.org
2011-06-07 14:06 ` kkojima at gcc dot gnu.org
2011-06-08 14:03 ` kkojima at gcc dot gnu.org [this message]
2011-06-08 23:14 ` kkojima at gcc dot gnu.org
2011-06-08 23:17 ` kkojima 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-49305-4-phVgu1HDS9@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).