public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ienkovich at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/67761] [6 Regression] Bootstrap failure on x86 Date: Tue, 29 Sep 2015 15:41:00 -0000 [thread overview] Message-ID: <bug-67761-4-T3fhYkrFEF@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-67761-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67761 Ilya Enkovich <ienkovich at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |ASSIGNED Last reconfirmed| |2015-09-29 Assignee|unassigned at gcc dot gnu.org |ienkovich at gcc dot gnu.org Ever confirmed|0 |1 --- Comment #1 from Ilya Enkovich <ienkovich at gcc dot gnu.org> --- The problem is in debug insns which are not ignored by introduced transformation. It results in cost model affected by debug info and causes these comparison failures. I'm testing this fix: diff --git a/gcc/config/i386/i386.c b/gcc/config/i386/i386.c index 6f2380f..7b3ffb0 100644 --- a/gcc/config/i386/i386.c +++ b/gcc/config/i386/i386.c @@ -2919,6 +2919,10 @@ scalar_chain::analyze_register_chain (bitmap candidates, df_ref ref) for (chain = DF_REF_CHAIN (ref); chain; chain = chain->next) { unsigned uid = DF_REF_INSN_UID (chain->ref); + + if (!NONDEBUG_INSN_P (DF_REF_INSN (chain->ref))) + continue; + if (!DF_REF_REG_MEM_P (chain->ref)) { if (bitmap_bit_p (insns, uid)) @@ -3279,7 +3283,7 @@ scalar_chain::convert_reg (unsigned regno) bitmap_clear_bit (conv, DF_REF_INSN_UID (ref)); } } - else + else if (NONDEBUG_INSN_P (DF_REF_INSN (ref))) { replace_rtx (DF_REF_INSN (ref), reg, scopy); df_insn_rescan (DF_REF_INSN (ref));
next prev parent reply other threads:[~2015-09-29 15:41 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-09-29 12:10 [Bug bootstrap/67761] New: " hjl.tools at gmail dot com 2015-09-29 13:14 ` [Bug bootstrap/67761] " rguenth at gcc dot gnu.org 2015-09-29 15:41 ` ienkovich at gcc dot gnu.org [this message] 2015-09-30 15:16 ` ienkovich 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-67761-4-T3fhYkrFEF@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).