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/61844] ICE when building libgcc for sh64 cross-compiler
Date: Mon, 28 Jul 2014 05:48:00 -0000 [thread overview]
Message-ID: <bug-61844-4-mq2GC2ralF@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61844-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61844
--- Comment #9 from Kazumoto Kojima <kkojima at gcc dot gnu.org> ---
The testcase in #7 can be compiled successfully when -mindexed-addressing
is added. It looks that base+index reg addressing mode is disabled
for shmedia32 and shcompact as default and it makes ira unhappy.
We used to return NO_REGS for INDEX_REG_CLASS when -mindexed-addressing
is disabled and it could suppress the use of reg+index addressing in
the older compilers. It seems that now this isn't the right way to
disable that addressing. With
--- /svn/trunk/gcc/config/sh/sh.h 2014-05-14 10:20:06.526008871 +0900
+++ gcc/config/sh/sh.h 2014-07-28 14:16:51.358771570 +0900
@@ -1723,8 +1723,7 @@ struct sh_args {
#define INDEX_REGISTER_RTX_P(X) MAYBE_INDEX_REGISTER_RTX_P(X, false)
#endif
-#define ALLOW_INDEXED_ADDRESS \
- ((!TARGET_SHMEDIA32 && !TARGET_SHCOMPACT) || TARGET_ALLOW_INDEXED_ADDRESS)
+#define ALLOW_INDEXED_ADDRESS 1
/* A C compound statement that attempts to replace X, which is an address
that needs reloading, with a valid memory address for an operand of
my c-only sh64-elf build is completed without errors. Although
I don't think the patch does the right thing, it'll prove that
ALLOW_INDEXED_ADDRESS causes problems.
next prev parent reply other threads:[~2014-07-28 5:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-18 14:05 [Bug c/61844] New: " dhowells at redhat dot com
2014-07-18 14:22 ` [Bug c/61844] " dhowells at redhat dot com
2014-07-18 14:25 ` dhowells at redhat dot com
2014-07-18 14:28 ` dhowells at redhat dot com
2014-07-18 14:31 ` dhowells at redhat dot com
2014-07-27 20:33 ` [Bug rtl-optimization/61844] " olegendo at gcc dot gnu.org
2014-07-28 0:29 ` [Bug target/61844] " kkojima at gcc dot gnu.org
2014-07-28 1:11 ` kkojima at gcc dot gnu.org
2014-07-28 5:48 ` kkojima at gcc dot gnu.org [this message]
2014-07-28 21:57 ` olegendo at gcc dot gnu.org
2014-07-29 21:31 ` olegendo at gcc dot gnu.org
2014-07-31 16:06 ` dhowells at redhat dot com
2014-07-31 16:28 ` olegendo at gcc dot gnu.org
2014-07-31 20:20 ` olegendo at gcc dot gnu.org
2014-07-31 21:16 ` 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-61844-4-mq2GC2ralF@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).