public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "abel at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/56957] [4.9 regression] ICE in add_insn_after, at emit-rtl.c:3783 Date: Wed, 17 Apr 2013 05:14:00 -0000 [thread overview] Message-ID: <bug-56957-4-vMekFC5N4S@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-56957-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56957 --- Comment #4 from Andrey Belevantsev <abel at gcc dot gnu.org> 2013-04-17 05:14:44 UTC --- (In reply to comment #2) > Breakpoint 5, sel_remove_insn (insn=0x3fffb5da4e78, only_disconnect=false, > full_tidying=false) at ../../trunk/gcc/sel-sched-ir.c:3938 > 3938 delete_insn (insn); > 1: debug_rtx(insn) = (insn 303 190 191 10 (set (reg:DF 165 f37 [421]) > (unspec:DF [ > (mem:DF (reg/f:DI 18 r18 [420]) [2 *a_7(D) S8 A64]) > ] UNSPEC_LDA)) 13 {movdf_advanced} > (nil)) You are right, this is not supposed to happen. The only_disconnect business is for the unification and transformation support, when you have possibly several insns as sources of the one chosen for scheduling. Thus, you need to delete all sources but the one you're going to move upwards, and even this chosen one should be deleted if it was changed while moving. The insn in question is a speculative insn possibly generated earlier, so ... > (gdb) p EXPR_WAS_CHANGED(expr) > $22 = true ... if this is true, we are supposed to emit the new insn obviously with the new id. The issue is that we then decide to emit the very same insn. I will take a look.
next prev parent reply other threads:[~2013-04-17 5:14 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-04-14 19:40 [Bug rtl-optimization/56957] New: " schwab@linux-m68k.org 2013-04-15 10:12 ` [Bug rtl-optimization/56957] " rguenth at gcc dot gnu.org 2013-04-16 20:22 ` steven at gcc dot gnu.org 2013-04-16 20:35 ` steven at gcc dot gnu.org 2013-04-16 20:54 ` steven at gcc dot gnu.org 2013-04-16 21:36 ` steven at gcc dot gnu.org 2013-04-17 5:14 ` abel at gcc dot gnu.org [this message] 2013-04-17 6:52 ` abel at gcc dot gnu.org 2013-04-18 9:08 ` steven at gcc dot gnu.org 2013-04-18 9:18 ` abel at gcc dot gnu.org 2013-04-22 9:48 ` abel at gcc dot gnu.org 2013-04-25 10:03 ` abel at gcc dot gnu.org 2013-04-30 10:58 ` abel 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-56957-4-vMekFC5N4S@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).