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/102893] [9/10/11 Regression] CDDCE does not detect empty infinite nested loops Date: Thu, 17 Feb 2022 11:26:17 +0000 [thread overview] Message-ID: <bug-102893-4-jl6Fs9q8nh@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102893-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102893 --- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-11 branch has been updated by Richard Biener <rguenth@gcc.gnu.org>: https://gcc.gnu.org/g:6d9c2ed02128ddf327465333f5563500b6cf8886 commit r11-9587-g6d9c2ed02128ddf327465333f5563500b6cf8886 Author: Richard Biener <rguenther@suse.de> Date: Fri Oct 22 12:45:32 2021 +0200 tree-optimization/102893 - properly DCE empty loops inside infinite loops The following fixes the test for an exit edge I put in place for the fix for PR45178 where I somehow misunderstood how the cyclic list works. 2021-10-22 Richard Biener <rguenther@suse.de> PR tree-optimization/102893 * tree-ssa-dce.c (find_obviously_necessary_stmts): Fix the test for an exit edge. * gcc.dg/tree-ssa/ssa-dce-9.c: New testcase. (cherry picked from commit c2a9a98a369528c8689ecb68db576f8e7dc2fa45)
next prev parent reply other threads:[~2022-02-17 11:26 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-22 9:40 [Bug tree-optimization/102893] New: [8/9/10/11/12 " tnfchris at gcc dot gnu.org 2021-10-22 10:44 ` [Bug tree-optimization/102893] [9/10/11/12 " rguenth at gcc dot gnu.org 2021-10-22 11:43 ` cvs-commit at gcc dot gnu.org 2021-10-22 11:43 ` [Bug tree-optimization/102893] [9/10/11 " rguenth at gcc dot gnu.org 2021-10-22 12:07 ` tnfchris at gcc dot gnu.org 2022-02-17 10:17 ` rguenth at gcc dot gnu.org 2022-02-17 11:26 ` cvs-commit at gcc dot gnu.org [this message] 2022-05-27 9:46 ` [Bug tree-optimization/102893] [10 " rguenth at gcc dot gnu.org 2022-06-28 10:46 ` jakub at gcc dot gnu.org 2023-07-07 9:47 ` 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-102893-4-jl6Fs9q8nh@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).