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/105755] -Wanalyzer-null-dereference regression compiling Emacs Date: Thu, 09 Mar 2023 21:21:33 +0000 [thread overview] Message-ID: <bug-105755-4-6BaVUUYOFO@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105755-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105755 --- Comment #1 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:4214bdb1d77ebee04d12f66c831730ed67fedf55 commit r13-6565-g4214bdb1d77ebee04d12f66c831730ed67fedf55 Author: David Malcolm <dmalcolm@redhat.com> Date: Thu Mar 9 16:21:02 2023 -0500 testsuite: add various -Wanalyzer-null-dereference false +ve test cases There are various -Wanalyzer-null-dereference false +ves in bugzilla that I've been attempting to fix. Unfortunately I haven't made much progress, but it seems worth at least capturing the reduced reproducers as test cases, to make it easier to spot changes in behavior. gcc/testsuite/ChangeLog: PR analyzer/102671 PR analyzer/105755 PR analyzer/108251 PR analyzer/108400 * gcc.dg/analyzer/null-deref-pr102671-1.c: New test, reduced from Emacs. * gcc.dg/analyzer/null-deref-pr102671-2.c: Likewise. * gcc.dg/analyzer/null-deref-pr105755.c: Likewise. * gcc.dg/analyzer/null-deref-pr108251-smp_fetch_ssl_fc_has_early-O2.c: New test, reduced from haproxy's src/ssl_sample.c. * gcc.dg/analyzer/null-deref-pr108251-smp_fetch_ssl_fc_has_early.c: Likewise. * gcc.dg/analyzer/null-deref-pr108400-SoftEtherVPN-WebUi.c: New test, reduced from SoftEtherVPN's src/Cedar/WebUI.c. Signed-off-by: David Malcolm <dmalcolm@redhat.com>
next prev parent reply other threads:[~2023-03-09 21:21 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-28 3:49 [Bug analyzer/105755] New: " eggert at cs dot ucla.edu 2023-03-09 21:21 ` cvs-commit at gcc dot gnu.org [this message] 2024-01-28 8:19 ` [Bug analyzer/105755] " nightstrike at gmail dot com 2024-02-16 14:35 ` dmalcolm at gcc dot gnu.org 2024-02-16 14:39 ` dmalcolm at gcc dot gnu.org 2024-02-16 19:35 ` nightstrike at gmail dot com 2024-02-16 19:39 ` nightstrike at gmail dot com 2024-02-16 19:41 ` iains 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-105755-4-6BaVUUYOFO@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).