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/107345] - -Wanayzer-null-dereference false positive with giving weird path infomation Date: Mon, 24 Oct 2022 14:35:44 +0000 [thread overview] Message-ID: <bug-107345-4-TdcBqyFU0Y@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107345-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107345 David Malcolm <dmalcolm at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |ASSIGNED Last reconfirmed| |2022-10-24 --- Comment #1 from David Malcolm <dmalcolm at gcc dot gnu.org> --- Thanks for filing this bug. The analyzer is seeing NULL == &e and fails to treat this as being false; the logic for spotting comparison of &VAR against NULL was only looking for NULL on the right-hand side. I'm working on a fix.
next prev parent reply other threads:[~2022-10-24 14:35 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-21 9:52 [Bug analyzer/107345] New: " geoffreydgr at icloud dot com 2022-10-24 14:35 ` dmalcolm at gcc dot gnu.org [this message] 2022-10-24 20:49 ` [Bug analyzer/107345] " cvs-commit at gcc dot gnu.org 2022-10-24 21:02 ` dmalcolm at gcc dot gnu.org 2022-10-28 15:54 ` geoffreydgr at icloud dot com 2022-10-28 15:56 ` geoffreydgr at icloud dot com 2023-03-29 18:18 ` [Bug analyzer/107345] -Wanalyzer-null-dereference " cvs-commit at gcc dot gnu.org 2023-03-29 19:15 ` dmalcolm 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-107345-4-TdcBqyFU0Y@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).