public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug analyzer/108806] -Wanalyzer-null-dereference false positives due to not handling bitmasks Date: Thu, 16 Feb 2023 23:20:46 +0000 [thread overview] Message-ID: <bug-108806-4-bOS60Kd1p4@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108806-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108806 David Malcolm <dmalcolm at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Last reconfirmed| |2023-02-16 Status|UNCONFIRMED |ASSIGNED --- Comment #2 from David Malcolm <dmalcolm at gcc dot gnu.org> --- Should be fixed on trunk for GCC 13 by the above commit. Keeping this open to track backporting the fix to GCC 12. I rewrote switch-handling in GCC 12, so I don't think this is going to be backportable to 11 or 10.
next prev parent reply other threads:[~2023-02-16 23:20 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-15 16:36 [Bug analyzer/108806] New: " dmalcolm at gcc dot gnu.org 2023-02-16 23:14 ` [Bug analyzer/108806] " cvs-commit at gcc dot gnu.org 2023-02-16 23:20 ` dmalcolm at gcc dot gnu.org [this message] 2024-04-14 5:06 ` [Bug analyzer/108806] [12 Regression] " pinskia at gcc dot gnu.org 2024-06-20 9:11 ` 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-108806-4-bOS60Kd1p4@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).