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/110520] -Wanalyzer-null-dereference false nagetive with `*ptr = 10086`
Date: Wed, 06 Sep 2023 21:37:07 +0000 [thread overview]
Message-ID: <bug-110520-4-7icjw5twMj@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110520-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110520
David Malcolm <dmalcolm at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2023-09-06
--- Comment #1 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
Thanks for filing this bug.
With trunk (for gcc 14) I correctly get a NPD warning (true positive):
https://godbolt.org/z/a5h38cz7d
With gcc 13.2, I don't (false negative):
https://godbolt.org/z/PKnToYK8v
I've been rewriting C string handling for gcc 14, so it's likely this now
working is a side-effect of that.
Keeping open to track adding a regression test for this.
next prev parent reply other threads:[~2023-09-06 21:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-02 12:30 [Bug analyzer/110520] New: " dale.mengli.ming at proton dot me
2023-09-06 21:37 ` dmalcolm at gcc dot gnu.org [this message]
2023-10-25 8:18 ` [Bug analyzer/110520] " dale.mengli.ming at proton dot me
2024-02-19 23:10 ` [Bug analyzer/110520] -Wanalyzer-null-dereference false negative " cvs-commit at gcc dot gnu.org
2024-02-19 23: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-110520-4-7icjw5twMj@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).