From: Jeff Law <jeffreyalaw@gmail.com>
To: Hans-Peter Nilsson <hp@axis.com>
Cc: gcc-patches@gcc.gnu.org, Martin Uecker <uecker@tugraz.at>,
richard.guenther@gmail.com
Subject: Re: Ping: [PATCH] Fix PR112419
Date: Fri, 1 Dec 2023 07:57:42 -0700 [thread overview]
Message-ID: <1454d2f1-fd3e-480c-ada0-0b9e616163a5@gmail.com> (raw)
In-Reply-To: <20231130172705.72B95203CF@pchp3.se.axis.com>
On 11/30/23 10:27, Hans-Peter Nilsson wrote:
>>
>>
>> My plan was to split up the test case in one which is for
>> -Wstringop-overflow and one which is for -Wnonnull and then
>> one could turn off the -Wstringop-overflow for the tests
>> which are actually for -Wnonnull. But adding the dg-blah
>> would certainly be simpler.
>
> Sort-of-mid-week ping (only because status quo isn't clear):
> Jeff, are you content with Martin U:s reply (i.e. patch ok)
> or are you waiting for a follow-up?
>
> Perhaps it's already in your overflowing queue, then please
> ignore this, I'll just ping in a week. ;-)
>
> IMHO, after looking at the test-case I'd expect *more*
> warnings for ilp32 targets; i.e. it was a bug that it didn't
> show up before.
Sorry, not waiting on anything. Just crazy busy with some personal stuff.
I think we can go with the patch as-is.
Jeff
prev parent reply other threads:[~2023-12-01 14:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-31 19:05 [PATCH] Reduce false positives for -Wnonnull for VLA parameters [PR98541] Martin Uecker
2023-11-02 7:36 ` Richard Biener
2023-11-07 3:58 ` Hans-Peter Nilsson
2023-11-07 4:01 ` Jeff Law
2023-11-07 5:56 ` Martin Uecker
2023-11-16 4:24 ` Hans-Peter Nilsson
2023-11-23 17:05 ` Ping: [PATCH] Fix PR112419 (was: [PATCH] Reduce false positives for -Wnonnull for VLA parameters [PR98541]) Hans-Peter Nilsson
2023-11-27 15:36 ` Ping: [PATCH] Fix PR112419 Jeff Law
2023-11-27 15:54 ` Martin Uecker
2023-11-27 16:10 ` Martin Uecker
2023-11-30 17:27 ` Hans-Peter Nilsson
2023-12-01 14:57 ` Jeff Law [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=1454d2f1-fd3e-480c-ada0-0b9e616163a5@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hp@axis.com \
--cc=richard.guenther@gmail.com \
--cc=uecker@tugraz.at \
/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).