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/108367] [12/13 Regression] ICE: verify_ssa failed (error: definition in block 4 does not dominate use in block 3) since r12-5138-ge82c382971664d6f Date: Wed, 11 Jan 2023 12:50:56 +0000 [thread overview] Message-ID: <bug-108367-4-I6JsLQnI7z@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108367-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108367 --- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> --- The OACC parloops pass adds a loop-around edge which short-cuts the definition of the debug use. I don't see anywhere how that handles debug stmts - maybe it gets fixed during lowering ... (yes, with -fno-checking it looks OK after ompexpssa1). The offending rev. is most certainly not the cause of the actual issue.
next prev parent reply other threads:[~2023-01-11 12:50 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-11 11:45 [Bug tree-optimization/108367] New: [12/13 Regression] ICE: verify_ssa failed (error: definition in block 4 does not dominate use in block 3) asolokha at gmx dot com 2023-01-11 11:48 ` [Bug tree-optimization/108367] [12/13 Regression] ICE: verify_ssa failed (error: definition in block 4 does not dominate use in block 3) since r12-5138-ge82c382971664d6f marxin at gcc dot gnu.org 2023-01-11 12:50 ` rguenth at gcc dot gnu.org [this message] 2023-02-21 13:15 ` rguenth at gcc dot gnu.org 2023-05-08 12:26 ` [Bug tree-optimization/108367] [12/13/14 " 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-108367-4-I6JsLQnI7z@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).