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/90994] Bogus Wmaybe-uninitialized with fnon-call-exceptions Date: Wed, 31 Aug 2022 13:20:52 +0000 [thread overview] Message-ID: <bug-90994-4-3AnInk3jeW@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-90994-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90994 --- Comment #4 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:88f29a8aa82f2788baf2f9865940d4c83012c580 commit r13-2310-g88f29a8aa82f2788baf2f9865940d4c83012c580 Author: Richard Biener <rguenther@suse.de> Date: Wed Aug 31 14:04:46 2022 +0200 tree-optimization/90994 - fix uninit diagnostics with EH r12-3640-g94c12ffac234b2 sneaked in a hack to avoid the diagnostic for the testcase in PR90994 which sees non-call EH control flow confusing predicate analysis. The following patch instead adjusts the existing code handling EH to handle non-calls and do what I think was intented. PR tree-optimization/90994 * gimple-predicate-analysis.cc (predicate::init_from_control_deps): Ignore exceptional control flow and skip the edge for the purpose of predicate generation also for non-calls. * g++.dg/torture/pr90994.C: New testcase.
next prev parent reply other threads:[~2022-08-31 13:20 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-90994-4@http.gcc.gnu.org/bugzilla/> 2021-04-07 18:42 ` msebor at gcc dot gnu.org 2022-08-30 13:19 ` rguenth at gcc dot gnu.org 2022-08-31 12:11 ` rguenth at gcc dot gnu.org 2022-08-31 13:20 ` cvs-commit at gcc dot gnu.org [this message] 2022-08-31 13:23 ` 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-90994-4-3AnInk3jeW@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).