From: Markus Armbruster <armbru@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: Thomas Huth <thuth@redhat.com>,
qemu-devel@nongnu.org, pbonzini@redhat.com,
marcandre.lureau@redhat.com, berrange@redhat.com,
bcain@quicinc.com, imp@bsdimp.com, stefanha@redhat.com,
Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [PATCH 1/1] meson: Enable -Wshadow=local
Date: Thu, 26 Oct 2023 08:50:52 +0200 [thread overview]
Message-ID: <87a5s5dghf.fsf@pond.sub.org> (raw)
In-Reply-To: <5f330d44-6e42-3275-8be6-8b06cb40f093@linaro.org> ("Philippe Mathieu-Daudé"'s message of "Thu, 26 Oct 2023 08:17:55 +0200")
Philippe Mathieu-Daudé <philmd@linaro.org> writes:
> On 26/10/23 08:12, Thomas Huth wrote:
>> On 26/10/2023 07.58, Philippe Mathieu-Daudé wrote:
[...]
>>> $ ../configure
>>> The Meson build system
>>> Version: 1.2.1
>>> Build type: native build
>>> Project name: qemu
>>> Project version: 8.1.50
>>> C compiler for the host machine: cc (clang 15.0.0 "Apple clang version 15.0.0 (clang-1500.0.40.1)")
>>> C linker for the host machine: cc ld64 1015.7
>>> Host machine cpu family: aarch64
>>> Host machine cpu: aarch64
>>> Program sh found: YES (/bin/sh)
>>> Objective-C compiler for the host machine: clang (clang 15.0.0)
>>> Objective-C linker for the host machine: clang ld64 1015.7
>
>
>>> Compiler for Objective-C supports arguments -Wshadow=local: NO
>>>
>>> So:
>>>
>>> Tested-by: Philippe Mathieu-Daudé <philmd@linaro.org>
>>> Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
Thanks!
>>> Now don't blame me for posting patches with trigger shadow=local
>>> warnings because I am not testing that locally.
>>>
>>> I find it a bit unfair to force me rely on CI or other machines
>>> rather than my host machine to check for warnings. I'd have
>>> rather waited this option support lands first in Clang before
>>> enabling this flag.
I'm not forcing anyone just yet, I'm merely posting a patch to solicit
feedback :)
PRO: It stops the backsliding. Thomas had to fix two new instances
already.
CON: Developers using only Clang may post patches that fail CI. We
don't know how annoying that will be in practice.
>> Huh, that situation is already pre-existing, e.g. with -Wimplicit-fallthrough=2 ... and if you're too afraid, you can always install gcc via homebrew to check.
>
> OK, fine.
I suggest to take the patch now, and if the CON turns out to outweigh
the PRO, revert it.
next prev parent reply other threads:[~2023-10-26 6:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 5:31 [PATCH 0/1] Enable -Wshadow=local Markus Armbruster
2023-10-26 5:31 ` [PATCH 1/1] meson: " Markus Armbruster
2023-10-26 5:44 ` Thomas Huth
2023-10-26 5:51 ` Warner Losh
2023-10-26 5:55 ` Thomas Huth
2023-10-26 5:58 ` Philippe Mathieu-Daudé
2023-10-26 6:12 ` Thomas Huth
2023-10-26 6:17 ` Philippe Mathieu-Daudé
2023-10-26 6:50 ` Markus Armbruster [this message]
2023-10-26 10:05 ` Daniel P. Berrangé
2023-10-26 5:54 ` [PATCH 0/1] " Warner Losh
2023-10-27 0:52 ` Stefan Hajnoczi
2023-10-27 2:25 ` Brian Cain
2023-10-27 4:41 ` Markus Armbruster
2023-10-30 4:58 ` Stefan Hajnoczi
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=87a5s5dghf.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=bcain@quicinc.com \
--cc=berrange@redhat.com \
--cc=imp@bsdimp.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=thuth@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.