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/65151] [SH][4.9 Regression] Internal compiler error when trying to build libav 11.2 on sh4
Date: Sat, 21 Feb 2015 23:26:00 -0000 [thread overview]
Message-ID: <bug-65151-4-4sG7OGHNul@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65151-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65151
--- Comment #7 from Oleg Endo <olegendo at gcc dot gnu.org> ---
The following fixes the problem:
Index: gcc/config/sh/sh.c
===================================================================
--- gcc/config/sh/sh.c (revision 220889)
+++ gcc/config/sh/sh.c (working copy)
@@ -12049,6 +12049,9 @@
bool
sh_hard_regno_mode_ok (unsigned int regno, enum machine_mode mode)
{
+ if (regno == T_REG)
+ return mode == SImode || mode == HImode || mode == QImode;
+
if (SPECIAL_REGISTER_P (regno))
return mode == SImode;
Index: gcc/config/sh/sh.md
===================================================================
--- gcc/config/sh/sh.md (revision 220889)
+++ gcc/config/sh/sh.md (working copy)
@@ -11224,6 +11224,13 @@
"movt %0"
[(set_attr "type" "arith")])
+(define_insn "*movt"
+ [(set (match_operand:QIHI 0 "arith_reg_dest" "=r")
+ (match_operand:QIHI 1 "t_reg_operand"))]
+ "TARGET_SH1"
+ "movt %0"
+ [(set_attr "type" "arith")])
+
(define_insn "movrt"
[(set (match_operand:SI 0 "arith_reg_dest" "=r")
(xor:SI (match_operand:SI 1 "t_reg_operand" "") (const_int 1)))]
However, I've not tested it for any further side effects.
next prev parent reply other threads:[~2015-02-21 22:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-21 4:48 [Bug c/65151] New: " glaubitz at physik dot fu-berlin.de
2015-02-21 13:29 ` [Bug target/65151] " olegendo at gcc dot gnu.org
2015-02-21 14:16 ` glaubitz at physik dot fu-berlin.de
2015-02-21 14:47 ` [Bug target/65151] [SH][4.9 Regression] " olegendo at gcc dot gnu.org
2015-02-21 21:29 ` olegendo at gcc dot gnu.org
2015-02-21 23:09 ` olegendo at gcc dot gnu.org
2015-02-21 23:26 ` olegendo at gcc dot gnu.org [this message]
2015-02-22 14:17 ` olegendo at gcc dot gnu.org
2015-02-23 0:00 ` kkojima at gcc dot gnu.org
2015-02-23 11:07 ` rguenth at gcc dot gnu.org
2015-06-26 19:59 ` jakub at gcc dot gnu.org
2015-06-26 20:30 ` jakub at gcc dot gnu.org
2015-08-08 14:54 ` thomas.petazzoni@free-electrons.com
2015-08-08 15:09 ` glaubitz at physik dot fu-berlin.de
2015-08-08 15:24 ` thomas.petazzoni@free-electrons.com
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-65151-4-4sG7OGHNul@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).