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/61844] ICE when building libgcc for sh64 cross-compiler Date: Thu, 31 Jul 2014 16:28:00 -0000 [thread overview] Message-ID: <bug-61844-4-NrgkQnwOiT@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 #13 from Oleg Endo <olegendo at gcc dot gnu.org> --- Author: olegendo Date: Thu Jul 31 16:27:56 2014 New Revision: 213381 URL: https://gcc.gnu.org/viewcvs?rev=213381&root=gcc&view=rev Log: gcc/ PR target/61844 * config/sh/sh.c (sh_legitimate_address_p, sh_legitimize_reload_address): Handle reg+reg address modes when ALLOW_INDEXED_ADDRESS is false. * config/sh/predicates.md (general_movsrc_operand, general_movdst_operand): Likewise. Modified: trunk/gcc/ChangeLog trunk/gcc/config/sh/predicates.md trunk/gcc/config/sh/sh.c
next prev parent reply other threads:[~2014-07-31 16:28 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 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 [this message] 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-NrgkQnwOiT@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: linkBe 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).