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/106722] bogus uninit warning in tree-vect-loop-manip.cc Date: Mon, 13 Feb 2023 07:27:05 +0000 [thread overview] Message-ID: <bug-106722-4-2Djc0Cgxyr@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106722-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106722 --- Comment #8 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:338739645b8e5bf34636d8d4829d7650001ad08c commit r13-5958-g338739645b8e5bf34636d8d4829d7650001ad08c Author: Richard Biener <rguenther@suse.de> Date: Fri Feb 10 10:28:29 2023 +0100 tree-optimization/106722 - fix CD-DCE edge marking The following fixes a latent issue when we mark control edges but end up with marking a block with no stmts necessary. In this case we fail to mark dependent control edges of that block. PR tree-optimization/106722 * tree-ssa-dce.cc (mark_last_stmt_necessary): Return whether we marked a stmt. (mark_control_dependent_edges_necessary): When mark_last_stmt_necessary didn't mark any stmt make sure to mark its control dependent edges. (propagate_necessity): Likewise. * gcc.dg/torture/pr108737.c: New testcase.
next prev parent reply other threads:[~2023-02-13 7:27 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-106722-4@http.gcc.gnu.org/bugzilla/> 2022-09-09 12:32 ` cvs-commit at gcc dot gnu.org 2022-10-17 12:32 ` rguenth at gcc dot gnu.org 2023-02-13 7:27 ` cvs-commit at gcc dot gnu.org [this message] 2023-12-06 10:45 ` 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-106722-4-2Djc0Cgxyr@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).