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/45178] CDDCE doesn't eliminate conditional code in infinite loop
Date: Fri, 27 Aug 2021 07:51:47 +0000 [thread overview]
Message-ID: <bug-45178-4-GKNcGcp402@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-45178-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=45178
--- Comment #5 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:41439e1f6d2da1e86538c726f0603cffd5dd098e
commit r12-3182-g41439e1f6d2da1e86538c726f0603cffd5dd098e
Author: Richard Biener <rguenther@suse.de>
Date: Fri Aug 27 09:47:49 2021 +0200
tree-optimization/45178 - DCE of dead control flow in infinite loop
This fixes DCE to be able to elide dead control flow in an
infinite loop without an exit edge. This special situation is
handled well by the code finding an edge to preserve since there's
no chance it will find the exit edge and make the loop finite.
2021-08-27 Richard Biener <rguenther@suse.de>
PR tree-optimization/45178
* tree-ssa-dce.c (find_obviously_necessary_stmts): For
infinite loops without exit do not mark control dependent
edges of the latch necessary.
* gcc.dg/tree-ssa/ssa-dce-3.c: Adjust testcase.
next prev parent reply other threads:[~2021-08-27 7:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-45178-4@http.gcc.gnu.org/bugzilla/>
2021-08-26 12:02 ` rguenth at gcc dot gnu.org
2021-08-26 14:35 ` hubicka at ucw dot cz
2021-08-27 7:51 ` cvs-commit at gcc dot gnu.org [this message]
2021-08-27 7:52 ` rguenth at gcc dot gnu.org
2022-02-17 11:26 ` cvs-commit at gcc dot gnu.org
2010-08-04 9:46 [Bug tree-optimization/45178] New: " rguenth at gcc dot gnu dot org
2010-08-04 13:05 ` [Bug tree-optimization/45178] " hubicka at ucw dot cz
2010-08-04 13:21 ` rguenth at gcc dot gnu dot 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-45178-4-GKNcGcp402@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).