public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "aldyh 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: Tue, 30 Nov 2021 12:12:27 +0000 [thread overview] Message-ID: <bug-99756-4-aLmETNgT7Q@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 Aldy Hernandez <aldyh at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED CC| |aldyh at gcc dot gnu.org Resolution|--- |FIXED --- Comment #2 from Aldy Hernandez <aldyh at gcc dot gnu.org> --- Fixed in trunk by one of the various improvements to the jump threader: abulafia:~/bld/t/gcc$ ./cc1 a.c -O2 -Wall -quiet abulafia:~/bld/t/gcc$ ./cc1 a.c -O2 -Wall -quiet -fno-thread-jumps a.c: In function ‘f’: a.c:10:10: warning: ‘x’ may be used uninitialized in this function [-Wmaybe-uninitialized] 10 | a[x] = 0; // { dg-bogus "Wmaybe-uninitialized" } | ~~~~~^~~ a.c:5:7: note: ‘x’ was declared here 5 | int x; | ^ abulafia:~/bld/t/gcc$
next prev parent reply other threads:[~2021-11-30 12:12 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 ` [Bug tree-optimization/99756] " msebor at gcc dot gnu.org 2021-11-30 12:12 ` aldyh at gcc dot gnu.org [this message] 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-aLmETNgT7Q@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).