public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/97539] [10/11 Regression] ICE verify_ssa failed since r10-4200-gb7ff7cef5005721e
Date: Mon, 26 Oct 2020 09:07:47 +0000	[thread overview]
Message-ID: <bug-97539-4-bTd7nisHBV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97539-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97539

--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
So the fundamental issue is that we have a debug-only live use and we do not
have LC SSA for those.  When vectorizer epilogue peeling then creates the
loop copy the debug use is still refering to the first loop but that def
no longer dominates the use because of the branch to the epilogue skipping
the vectorized loop.

The simplest workaround would be to first to a sweep over the original
loop body searching for such uses and resetting the corresponding debug binds.

  parent reply	other threads:[~2020-10-26  9:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-23  7:42 [Bug c/97539] New: error: definition in block 5 does not dominate use in block 24 dcb314 at hotmail dot com
2020-10-23  8:51 ` [Bug tree-optimization/97539] [10/11 Regression] ICE verify_ssa failed since r10-4200-gb7ff7cef5005721e marxin at gcc dot gnu.org
2020-10-23 11:47 ` rguenth at gcc dot gnu.org
2020-10-26  9:07 ` rguenth at gcc dot gnu.org [this message]
2020-10-26 10:34 ` cvs-commit at gcc dot gnu.org
2020-10-26 10:35 ` [Bug tree-optimization/97539] [10 " rguenth at gcc dot gnu.org
2020-12-01 15:44 ` cvs-commit at gcc dot gnu.org
2020-12-01 15:46 ` rguenth 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-97539-4-bTd7nisHBV@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).