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/96598] false NULL argument warning [-Wanalyzer-null-argument] Date: Thu, 13 Aug 2020 23:09:04 +0000 [thread overview] Message-ID: <bug-96598-4-iPt65bL8ZK@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96598-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96598 --- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by David Malcolm <dmalcolm@gcc.gnu.org>: https://gcc.gnu.org/g:2ec32ddf822887cddc8910ed30dc105890def4ee commit r11-2695-g2ec32ddf822887cddc8910ed30dc105890def4ee Author: David Malcolm <dmalcolm@redhat.com> Date: Thu Aug 13 15:11:10 2020 -0400 analyzer: add regression test [PR96598] PR analyzer/96598 reports that -fanalyzer issues a false warning: use of NULL 'str' where non-null expected with gcc 10.2 when used with -fsanitize=undefined. This was fixed by g:808f4dfeb3a95f50f15e71148e5c1067f90a126d. gcc/testsuite/ChangeLog: PR analyzer/96598 * gcc.dg/analyzer/pr96598.c: New test.
next prev parent reply other threads:[~2020-08-13 23:09 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-08-13 7:40 [Bug c/96598] New: " dpotapov at gmail dot com 2020-08-13 20:41 ` [Bug analyzer/96598] " dmalcolm at gcc dot gnu.org 2020-08-13 23:09 ` cvs-commit at gcc dot gnu.org [this message] 2020-08-13 23:11 ` 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-96598-4-iPt65bL8ZK@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).