From: Martin Sebor <msebor@gmail.com>
To: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: [pushed] correct/improve handling of null VLA arguments (PR 97188)
Date: Tue, 29 Sep 2020 17:15:20 -0600 [thread overview]
Message-ID: <9897cf44-869c-0da2-1ee5-f2e40b8df4df@gmail.com> (raw)
In-Reply-To: <76459e14-ce07-db88-f7b9-ec9bad7715a3@gmail.com>
I have committed & pushed the fix in r11-3540.
On 9/24/20 6:15 PM, Martin Sebor wrote:
> The machinery recently added to support -Warray-parameter and
> -Wvla-parameter also results in enhanced detection of null
> pointer arguments to VLA function parameters. This enhancement
> wasn't tested as comprehensively as it should have been and
> so has some bugs. The attached patch fixes one that leads
> to an ICE. It also restructures the function and improves
> the warning issues in this case.
>
> The fix is slightly bit bigger than what I would normally commit
> without a review but since it's all in code I just wrote and in
> my view low risk I will go ahead and push it in a few days unless
> I hear requests for changes by then.
>
> Martin
prev parent reply other threads:[~2020-09-29 23:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-25 0:15 [PATCH] " Martin Sebor
2020-09-29 23:15 ` Martin Sebor [this message]
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=9897cf44-869c-0da2-1ee5-f2e40b8df4df@gmail.com \
--to=msebor@gmail.com \
--cc=gcc-patches@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).