public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug analyzer/107345] -Wanalyzer-null-dereference false positive with giving weird path infomation Date: Wed, 29 Mar 2023 18:18:25 +0000 [thread overview] Message-ID: <bug-107345-4-mcRqQ4iPOt@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 --- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-12 branch has been updated by David Malcolm <dmalcolm@gcc.gnu.org>: https://gcc.gnu.org/g:111fb5d3cafd0f7f2a0d01aa9e1213013fa0cc83 commit r12-9357-g111fb5d3cafd0f7f2a0d01aa9e1213013fa0cc83 Author: David Malcolm <dmalcolm@redhat.com> Date: Wed Mar 29 14:16:47 2023 -0400 analyzer: handle (NULL == &VAR) [PR107345] Cherrypicked from r13-3468-g18faaeb3af42f3. gcc/analyzer/ChangeLog: PR analyzer/107345 * region-model.cc (region_model::eval_condition_without_cm): Ensure that constants are on the right-hand side before checking for them. gcc/testsuite/ChangeLog: PR analyzer/107345 * gcc.dg/analyzer/pr107345.c: New test. Signed-off-by: David Malcolm <dmalcolm@redhat.com>
next prev parent reply other threads:[~2023-03-29 18:18 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-21 9:52 [Bug analyzer/107345] New: - -Wanayzer-null-dereference " geoffreydgr at icloud dot com 2022-10-24 14:35 ` [Bug analyzer/107345] " dmalcolm at gcc dot gnu.org 2022-10-24 20:49 ` 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 ` cvs-commit at gcc dot gnu.org [this message] 2023-03-29 19:15 ` [Bug analyzer/107345] -Wanalyzer-null-dereference " 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-mcRqQ4iPOt@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).