public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/99756] bogus -Wmaybe-uninitialized with a use conditional that's a subset of a defining conditional Date: Wed, 24 Mar 2021 23:51:28 +0000 [thread overview] Message-ID: <bug-99756-4-C5KjWeqRo0@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99756-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99756 Martin Sebor <msebor at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |diagnostic Depends on| |99755 Blocks| |24639 Known to fail| |10.2.0, 11.0, 4.1.0, 4.8.4, | |4.9.4, 5.5.0, 6.4.0, 7.2.0, | |8.3.0, 9.1.0 --- Comment #1 from Martin Sebor <msebor at gcc dot gnu.org> --- The spurious warning goes as far back as GCC 4.1. It can be avoided either by improving the optimization or by changing tree-ssa-uninit.c. Referenced Bugs: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=24639 [Bug 24639] [meta-bug] bug to track all Wuninitialized issues https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99755 [Bug 99755] failure to fold a conditional that's a subset of another expression
next prev parent reply other threads:[~2021-03-24 23:51 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-24 23:48 [Bug tree-optimization/99756] New: " msebor at gcc dot gnu.org 2021-03-24 23:51 ` msebor at gcc dot gnu.org [this message] 2021-11-30 12:12 ` [Bug tree-optimization/99756] " aldyh at gcc dot gnu.org 2021-12-18 11:47 ` 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-99756-4-C5KjWeqRo0@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).