public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "alexey.lapshin at espressif dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug analyzer/109131] -Wanalyzer-deref-before-check false positive seen in git's builtin/show-ref.c
Date: Fri, 27 Oct 2023 17:50:42 +0000	[thread overview]
Message-ID: <bug-109131-4-in1bysBYRM@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109131-4@http.gcc.gnu.org/bugzilla/>

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

Alexey <alexey.lapshin at espressif dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |alexey.lapshin at espressif dot co
                   |                            |m

--- Comment #1 from Alexey <alexey.lapshin at espressif dot com> ---
There is a smaller reproducer:

```
struct a {
    int b;
};
void foo(struct a *p) {
    if (p->b)
        p = 0;
    if (p && p->b)   // "p" can be 0 but warning
        ;
}
```

  reply	other threads:[~2023-10-27 17:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-14 19:30 [Bug analyzer/109131] New: " dmalcolm at gcc dot gnu.org
2023-10-27 17:50 ` alexey.lapshin at espressif dot com [this message]
2024-02-15 19:56 ` [Bug analyzer/109131] [13/14 Regression] " dmalcolm at gcc dot gnu.org
2024-03-04 13:00 ` rguenth at gcc dot gnu.org
2024-03-08 15:38 ` law at gcc dot gnu.org
2024-05-21  9:14 ` [Bug analyzer/109131] [13/14/15 " jakub 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-109131-4-in1bysBYRM@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).