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/107289] - -Wanayzer-null-dereference false positive with  f = *b
Date: Mon, 17 Oct 2022 17:00:20 +0000	[thread overview]
Message-ID: <bug-107289-4-EAkwD8LUWh@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107289-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107289

David Malcolm <dmalcolm at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |ASSIGNED
   Last reconfirmed|                            |2022-10-17
     Ever confirmed|0                           |1

--- Comment #2 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
I believe that the analyzer is considering the case where "d" is (somehow)
called from outside of "main", and thus not making the assumption that *b ==
&a; seeing the compare with NULL, it considers the case that b could be NULL.

It's not yet clear to me that this case of d being called from outside "main"
is valid, or if it's always the case that d can only ever be called from main.

  parent reply	other threads:[~2022-10-17 17:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-17  9:59 [Bug analyzer/107289] New: " geoffreydgr at icloud dot com
2022-10-17 16:56 ` [Bug analyzer/107289] " dmalcolm at gcc dot gnu.org
2022-10-17 17:00 ` dmalcolm at gcc dot gnu.org [this message]
2022-10-18  2:45 ` geoffreydgr at icloud dot com

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-107289-4-EAkwD8LUWh@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: link
Be 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).