From: John Garry <john.garry@huawei.com>
To: Johannes Berg <johannes@sipsolutions.net>,
Joe Perches <joe@perches.com>,
Andrew Morton <akpm@linux-foundation.org>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Kalle Valo <kvalo@codeaurora.org>, <jakub.kicinski@netronome.com>,
<yamada.masahiro@socionext.com>, "Arnd Bergmann" <arnd@arndb.de>,
<viro@zeniv.linux.org.uk>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: <linux-wireless@vger.kernel.org>, <nbd@nbd.name>
Subject: Re: Question on FIELD_PREP() for static array
Date: Thu, 11 Oct 2018 17:16:41 +0100 [thread overview]
Message-ID: <ef2d37ab-bef4-fd3f-a6f7-e68e60695e9b@huawei.com> (raw)
In-Reply-To: <1539271422.3687.217.camel@sipsolutions.net>
On 11/10/2018 16:23, Johannes Berg wrote:
Hi
> On Thu, 2018-10-11 at 15:24 +0100, John Garry wrote:
>>
>>> +#define BUILD_BUG_ON_RET_ZERO(cond) (sizeof(char[1 - 2*!!(cond)]) - 1)
>>> +#define BUILD_BUG_ON_NOT_POW2_RET_ZERO(n) BUILD_BUG_ON_RET_ZERO(((n) & ((n) - 1)) != 0)
>
>> Seems reasonable. However I did try this and was getting compiler
>> warnings about VLA, from a non-constant being fed into
>> BUILD_BUG_ON_RET_ZERO(), related to sizeof char[]:
>> drivers/iio/adc/meson_saradc.c:375:2: warning: ISO C90 forbids variable
>> length array [-Wvla]
>> regval = FIELD_PREP(MESON_SAR_ADC_CHAN_LIST_ENTRY_MASK(0),
>
> Hmm, what's the code there?
Nothing special, it was just a sample. Here'e the code:
regval = FIELD_PREP(MESON_SAR_ADC_CHAN_LIST_ENTRY_MASK(0),
chan->address);
So val is a variable, and I find if remove both of the
BUILD_BUG_ON_RET_ZERO()' which use __bf_shf() then it goes away.
>
> I don't see why the compiler should think it's a variable length?
>
>> Surely __NLA_ENSURE is getting a similar issue as it uses a similar
>> principle, no? I see that this is in -next now, but could not this macro
>> or derivatives being referenced.
>
> Yeah, I have a patch now to reference it, but I don't see anything from
> -Wvla with gcc 8.1?
I'm using a 7.3.1-based toolchain
>
> See
> https://git.kernel.org/pub/scm/linux/kernel/git/jberg/mac80211-next.git/commit/?id=3d7af878357acd9e37fc156928106f1a969c8942
> and its parent.
>
> Do you see -Wvla warnings there? Any idea how I could reproduce them?
I'll try it, thanks
John
>
> johannes
>
> .
>
next prev parent reply other threads:[~2018-10-11 16:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-10 17:16 Question on FIELD_PREP() for static array John Garry
2018-10-10 17:33 ` Joe Perches
2018-10-10 18:13 ` Johannes Berg
2018-10-11 14:24 ` John Garry
2018-10-11 15:23 ` Johannes Berg
2018-10-11 16:16 ` John Garry [this message]
2018-10-11 17:26 ` John Garry
2018-10-11 19:13 ` Johannes Berg
2018-10-11 19:22 ` Johannes Berg
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=ef2d37ab-bef4-fd3f-a6f7-e68e60695e9b@huawei.com \
--to=john.garry@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=andy.shevchenko@gmail.com \
--cc=arnd@arndb.de \
--cc=jakub.kicinski@netronome.com \
--cc=joe@perches.com \
--cc=johannes@sipsolutions.net \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=nbd@nbd.name \
--cc=viro@zeniv.linux.org.uk \
--cc=yamada.masahiro@socionext.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