public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vmakarov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/63823] [5.0 Regression] MIPS will not build due to LRA ICE with 64 bit ABI
Date: Thu, 13 Nov 2014 14:46:00 -0000 [thread overview]
Message-ID: <bug-63823-4-DZWj4Az8CO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63823-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63823
--- Comment #6 from Vladimir Makarov <vmakarov at gcc dot gnu.org> ---
(In reply to Robert Suchanek from comment #5)
> It appears that enabling the debug info can trigger the ICE. In the
> testcase, after the patch, an instruction 1136 gets deleted and all
> references to pseudo 704 meant to be updated.
>
> The following change in process_bb_lives () triggers the assertion later in
> the pass.
>
> + EXECUTE_IF_SET_IN_BITMAP
> + (&lra_reg_info[dst_regno].insn_bitmap, 0, uid, bi)
> + {
> + insn = lra_insn_recog_data[uid]->insn;
> + lra_substitute_pseudo_within_insn (insn, dst_regno,
> + SET_SRC (set));
> + lra_update_insn_regno_info (insn);
> + }
>
> On the first iteration, the list of insns using pseudo 704 is correct:
>
> (gdb) call debug_bitmap(&lra_reg_info[704].insn_bitmap)
>
> first = 0x188b720 current = 0x188b770 indx = 3
> 0x188b720 next = 0x188b770 prev = (nil) indx = 2
> bits = { 343 }
> 0x188b770 next = (nil) prev = 0x188b720 indx = 3
> bits = { 384 }
>
> Insn 343 gets updated, pseudo 704 is replaced with original pseudo 234.
> However, the call to lra_update_insn_regno_info destroys the remaining
> references to pseudo 704 via invalidate_insn_data_regno_info so we end up
> with the following:
>
> (gdb) call debug_bitmap(&lra_reg_info[704].insn_bitmap)
>
> first = 0x1855770 current = 0x1855770 indx = 3
> 0x1855770 next = (nil) prev = (nil) indx = 3
> bits = { 384 }
>
> The next iteration(s) in EXECUTE_IF_SET_IN_BITMAP will not happen as
> bmp_iter_set () returns false. Insn 384 is left unchanged and the compiler
> fails later on assertion.
Thanks for analyzing this, Robert. I've been working on some LRA
rematerialization issues and found this too. I'll post a patch fixing this
issue soon. If it works for you, I'll commit it on this week.
next prev parent reply other threads:[~2014-11-13 14:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-11 18:00 [Bug rtl-optimization/63823] New: " sje at gcc dot gnu.org
2014-11-11 18:01 ` [Bug rtl-optimization/63823] " sje at gcc dot gnu.org
2014-11-11 18:05 ` pinskia at gcc dot gnu.org
2014-11-11 18:15 ` sje at gcc dot gnu.org
2014-11-12 9:45 ` rguenth at gcc dot gnu.org
2014-11-13 14:46 ` vmakarov at gcc dot gnu.org [this message]
2014-11-13 14:52 ` vmakarov at gcc dot gnu.org
2014-11-13 16:12 ` robert.suchanek at imgtec dot com
2014-11-20 16:12 ` vmakarov at gcc dot gnu.org
2014-11-20 16:19 ` sje 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-63823-4-DZWj4Az8CO@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).