public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "kkojima at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/37909] internal compiler error: in fixup_mova, at config/sh/sh.c:3756 Date: Sun, 26 Oct 2008 08:27:00 -0000 [thread overview] Message-ID: <20081026082622.29442.qmail@sourceware.org> (raw) In-Reply-To: <bug-37909-16403@http.gcc.gnu.org/bugzilla/> ------- Comment #4 from kkojima at gcc dot gnu dot org 2008-10-26 08:26 ------- sh_reorg might insert a new mova in SH_FIXUP_PCLOAD phase. When untangle_mova looks this mova insn, it may not be associated with the insn address yet but the current code takes its undefined address. It seems that this mova should be skipped there because it will be handled later. I'm testing the attached patch. -- * config/sh/sh.c (untangle_mova): Return -1 when NEW_MOVA has no address. --- ORIG/trunk/gcc/config/sh/sh.c 2008-10-22 09:11:15.000000000 +0900 +++ LOCAL/trunk/gcc/config/sh/sh.c 2008-10-26 10:36:59.000000000 +0900 @@ -3826,6 +3826,10 @@ untangle_mova (int *num_mova, rtx *first if (optimize) { + /* If NEW_MOVA has no address yet, it will be handled later. */ + if (INSN_ADDRESSES_SIZE() <= (unsigned) INSN_UID (new_mova)) + return -1; + n_addr = INSN_ADDRESSES (INSN_UID (new_mova)); n_target = INSN_ADDRESSES (INSN_UID (XEXP (MOVA_LABELREF (new_mova), 0))); if (n_addr > n_target || n_addr + 1022 < n_target) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37909
next prev parent reply other threads:[~2008-10-26 8:27 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-10-24 14:04 [Bug c++/37909] New: " masaki dot chikama at gmail dot com 2008-10-24 14:05 ` [Bug c++/37909] " masaki dot chikama at gmail dot com 2008-10-25 14:49 ` [Bug target/37909] " kkojima at gcc dot gnu dot org 2008-10-25 14:54 ` kkojima at gcc dot gnu dot org 2008-10-26 8:27 ` kkojima at gcc dot gnu dot org [this message] 2008-10-29 23:54 ` kkojima at gcc dot gnu dot org 2008-10-31 3:47 ` kkojima at gcc dot gnu dot org 2008-10-31 3:54 ` kkojima at gcc dot gnu dot org 2008-10-31 13:25 ` kkojima at gcc dot gnu dot 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=20081026082622.29442.qmail@sourceware.org \ --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).