public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "olegendo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/56121] [SH] ICE in libgcc/unwind-dw2.c
Date: Sun, 27 Jan 2013 15:44:00 -0000 [thread overview]
Message-ID: <bug-56121-4-5n0xoUwQ87@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56121-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56121
Oleg Endo <olegendo at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target|sh*-*-* |sh2a-*-*
--- Comment #1 from Oleg Endo <olegendo at gcc dot gnu.org> 2013-01-27 15:44:23 UTC ---
This is an SH2A specific problem.
If I understand correctly, in this case two reloads for the failing bld_reg
insn are required, one for operands[0] and one for operands[1].
Applying the following:
Index: gcc/config/sh/sh.md
===================================================================
--- gcc/config/sh/sh.md (revision 195493)
+++ gcc/config/sh/sh.md (working copy)
@@ -13236,7 +13236,7 @@
(zero_extract:SI (match_operand:SI 0 "arith_reg_operand" "r")
(const_int 1)
(match_operand 1 "const_int_operand" "K03")))]
- "TARGET_SH2A"
+ "TARGET_SH2A && satisfies_constraint_K03 (operands[1])"
"bld %1,%0")
(define_insn "*bld_regqi"
fixes the problem. However, there are more insns of this type that might be
fail and probably should be modified as well...
next prev parent reply other threads:[~2013-01-27 15:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-27 12:26 [Bug target/56121] New: " olegendo at gcc dot gnu.org
2013-01-27 15:44 ` olegendo at gcc dot gnu.org [this message]
2013-01-27 16:24 ` [Bug target/56121] " olegendo at gcc dot gnu.org
2013-01-29 20:29 ` olegendo at gcc dot gnu.org
2013-01-29 20:33 ` olegendo 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-56121-4-5n0xoUwQ87@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).