public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/63660] -Wmaybe-uninitialized false positive on many repeated bitwise tests Date: Tue, 30 Aug 2022 08:01:37 +0000 [thread overview] Message-ID: <bug-63660-4-JiGXtr9Zg0@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-63660-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63660 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Known to work| |13.0 Status|NEW |RESOLVED Known to fail| |12.2.0 Resolution|--- |FIXED --- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> --- Confirmed with GCC 12 but it's been fixed on trunk. We do run into the MAX_POSTDOM_CHECK limit but r13-2155-gbaa3ffb19c54fa (and its dependence) solves this on trunk. I'm going to add the testcase.
next prev parent reply other threads:[~2022-08-30 8:01 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-10-27 18:32 [Bug driver/63660] New: [4.8-4.9+] -Wmaybe-uninitialized false positive with -O1 and more ed0.88.prez at gmail dot com 2014-10-28 9:04 ` [Bug tree-optimization/63660] " rguenth at gcc dot gnu.org 2014-12-03 14:15 ` [Bug tree-optimization/63660] -Wmaybe-uninitialized false positive (uninit pass limits) ed0.88.prez at gmail dot com 2014-12-03 14:52 ` manu at gcc dot gnu.org 2021-03-31 2:17 ` msebor at gcc dot gnu.org 2022-08-30 8:01 ` rguenth at gcc dot gnu.org [this message] 2022-08-30 8:05 ` [Bug tree-optimization/63660] -Wmaybe-uninitialized false positive on many repeated bitwise tests cvs-commit 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-63660-4-JiGXtr9Zg0@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).