public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/109331] ice: definition in block 7 does not dominate use in block 8
Date: Wed, 29 Mar 2023 11:56:35 +0000 [thread overview]
Message-ID: <bug-109331-4-FyRJ2aFWJq@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109331-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109331
--- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>:
https://gcc.gnu.org/g:86efc490ab86bfa00720479b4714da23cd7df797
commit r13-6928-g86efc490ab86bfa00720479b4714da23cd7df797
Author: Richard Biener <rguenther@suse.de>
Date: Wed Mar 29 11:59:16 2023 +0200
tree-optimization/109331 - make sure to clean up the CFG after forwprop
When forwprop discovers unreachable code or makes decisions based
on unreachable edges make sure to cleanup the CFG since otherwise
SSA form can become invalid.
PR tree-optimization/109331
* tree-ssa-forwprop.cc (pass_forwprop::execute): When we
discover a taken edge make sure to cleanup the CFG.
* gcc.dg/torture/pr109331.c: New testcase.
next prev parent reply other threads:[~2023-03-29 11:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-29 8:56 [Bug c/109331] New: " dcb314 at hotmail dot com
2023-03-29 9:53 ` [Bug tree-optimization/109331] " rguenth at gcc dot gnu.org
2023-03-29 11:56 ` cvs-commit at gcc dot gnu.org [this message]
2023-03-29 11:56 ` rguenth at gcc dot gnu.org
2023-03-29 16:08 ` [Bug tree-optimization/109331] [13 Regression] " pinskia 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-109331-4-FyRJ2aFWJq@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).