From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Brian Cain <bcain@quicinc.com>,
Taylor Simpson <ltaylorsimpson@gmail.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: "Matheus Bernardino (QUIC)" <quic_mathbern@quicinc.com>,
Sid Manning <sidneym@quicinc.com>,
"Marco Liebel (QUIC)" <quic_mliebel@quicinc.com>,
"richard.henderson@linaro.org" <richard.henderson@linaro.org>,
"ale@rev.ng" <ale@rev.ng>, "anjo@rev.ng" <anjo@rev.ng>
Subject: Re: [PATCH] Hexagon (target/hexagon) Fix shadow variable when idef-parser is off
Date: Fri, 1 Dec 2023 11:50:09 +0100 [thread overview]
Message-ID: <6d6d75e9-c7d3-4b62-ac8e-9aa3b09005c2@linaro.org> (raw)
In-Reply-To: <SN6PR02MB42057D4FC09929723903517AB882A@SN6PR02MB4205.namprd02.prod.outlook.com>
On 30/11/23 21:39, Brian Cain wrote:
>
>
>> -----Original Message-----
>> From: Philippe Mathieu-Daudé <philmd@linaro.org>
>> Sent: Thursday, November 30, 2023 2:17 PM
>> To: Taylor Simpson <ltaylorsimpson@gmail.com>; qemu-devel@nongnu.org
>> Cc: Brian Cain <bcain@quicinc.com>; Matheus Bernardino (QUIC)
>> <quic_mathbern@quicinc.com>; Sid Manning <sidneym@quicinc.com>; Marco
>> Liebel (QUIC) <quic_mliebel@quicinc.com>; richard.henderson@linaro.org;
>> ale@rev.ng; anjo@rev.ng
>> Subject: Re: [PATCH] Hexagon (target/hexagon) Fix shadow variable when idef-
>> parser is off
>>
>> WARNING: This email originated from outside of Qualcomm. Please be wary of
>> any links or attachments, and do not enable macros.
>>
>> On 30/11/23 19:39, Taylor Simpson wrote:
>>> Adding -Werror=shadow=compatible-local causes Hexagon not to build
>>> when idef-parser is off. The "label" variable in CHECK_NOSHUF_PRED
>>> shadows a variable in the surrounding code.
>>>
>>> Signed-off-by: Taylor Simpson <ltaylorsimpson@gmail.com>
>>> ---
>>> target/hexagon/macros.h | 6 +++---
>>> 1 file changed, 3 insertions(+), 3 deletions(-)
>>>
>>> diff --git a/target/hexagon/macros.h b/target/hexagon/macros.h
>>> index 9a51b5709b..f99390e2a8 100644
>>> --- a/target/hexagon/macros.h
>>> +++ b/target/hexagon/macros.h
>>> @@ -93,13 +93,13 @@
>>>
>>> #define CHECK_NOSHUF_PRED(GET_EA, SIZE, PRED) \
>>> do { \
>>> - TCGLabel *label = gen_new_label(); \
>>> - tcg_gen_brcondi_tl(TCG_COND_EQ, PRED, 0, label); \
>>> + TCGLabel *noshuf_label = gen_new_label(); \
>>> + tcg_gen_brcondi_tl(TCG_COND_EQ, PRED, 0, noshuf_label); \
>>
>> Fragile, but sufficient.
>
> The fragility here refers to the fact that CHECK_NOSHUF_PRED() macro could show up in other contexts and then could shadow those?
Yes.
> We could change the macro to a function or expand the macro to take a label declared outside. Would that be preferred? Or are there other suggestions?
Nah, this is good enough, no need to over-engineer IMHO
(I just wanted to remark this could still bit us in the
future, and -Werror will fire).
Regards,
Phil.
prev parent reply other threads:[~2023-12-01 10:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-30 18:39 [PATCH] Hexagon (target/hexagon) Fix shadow variable when idef-parser is off Taylor Simpson
2023-11-30 19:33 ` Brian Cain
2023-11-30 20:16 ` Philippe Mathieu-Daudé
2023-11-30 20:39 ` Brian Cain
2023-12-01 10:50 ` Philippe Mathieu-Daudé [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=6d6d75e9-c7d3-4b62-ac8e-9aa3b09005c2@linaro.org \
--to=philmd@linaro.org \
--cc=ale@rev.ng \
--cc=anjo@rev.ng \
--cc=bcain@quicinc.com \
--cc=ltaylorsimpson@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=quic_mathbern@quicinc.com \
--cc=quic_mliebel@quicinc.com \
--cc=richard.henderson@linaro.org \
--cc=sidneym@quicinc.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 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 NNTP newsgroup(s).