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 c/98541] warning with -Wnonnull for array parameter with bound > 0 Date: Fri, 03 Nov 2023 22:21:28 +0000 [thread overview] Message-ID: <bug-98541-4-VgoWJivI07@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98541-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98541 --- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Martin Uecker <uecker@gcc.gnu.org>: https://gcc.gnu.org/g:6e9ee44d96e5bda8808dd9d8ccf58d2525383f6b commit r14-5115-g6e9ee44d96e5bda8808dd9d8ccf58d2525383f6b Author: Martin Uecker <uecker@tugraz.at> Date: Thu Apr 13 19:35:15 2023 +0200 Reduce false positives for -Wnonnull for VLA parameters [PR98541] This patch limits the warning about NULL arguments to VLA parameters declared [static n]. PR c/98541 gcc/ * gimple-ssa-warn-access.cc (pass_waccess::maybe_check_access_sizes): For VLA bounds in parameters, only warn about null pointers with 'static'. gcc/testsuite: * gcc.dg/Wnonnull-4.c: Adapt test. * gcc.dg/Wstringop-overflow-40.c: Adapt test.
next prev parent reply other threads:[~2023-11-03 22:21 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-05 16:12 [Bug c/98541] New: " muecker at gwdg dot de 2021-01-06 18:08 ` [Bug c/98541] " msebor at gcc dot gnu.org 2021-01-06 18:12 ` msebor at gcc dot gnu.org 2021-01-06 19:06 ` muecker at gwdg dot de 2023-11-03 22:21 ` cvs-commit at gcc dot gnu.org [this message] 2023-11-04 10:01 ` uecker 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-98541-4-VgoWJivI07@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).