From: Lance Richardson <lrichard@redhat.com>
To: Stephen Boyd <sboyd@codeaurora.org>
Cc: linux-sparse@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Sparse warnings on GENMASK + arm32
Date: Wed, 26 Jul 2017 09:33:01 -0400 (EDT) [thread overview]
Message-ID: <1000702648.38599568.1501075981880.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20170726013020.GL2146@codeaurora.org>
> From: "Stephen Boyd" <sboyd@codeaurora.org>
> To: linux-sparse@vger.kernel.org
> Cc: linux-kernel@vger.kernel.org
> Sent: Tuesday, 25 July, 2017 9:30:20 PM
> Subject: Sparse warnings on GENMASK + arm32
>
> I see sparse warning when I check a clk driver file in the kernel
> on a 32-bit ARM build.
>
> drivers/clk/sunxi/clk-sun6i-ar100.c:65:20: warning: cast truncates bits from
> constant value (3ffffffff becomes ffffffff)
>
> The code in question looks like:
>
> static const struct factors_data sun6i_ar100_data = {
> .mux = 16,
> .muxmask = GENMASK(1, 0),
> .table = &sun6i_ar100_config,
> .getter = sun6i_get_ar100_factors,
> };
>
> where factors_data is
>
> struct factors_data {
> int enable;
> int mux;
> int muxmask;
> const struct clk_factors_config *table;
> void (*getter)(struct factors_request *req);
> void (*recalc)(struct factors_request *req);
> const char *name;
> };
>
>
> and sparse seems to be complaining about the muxmask assignment
> here. Oddly, this doesn't happen on arm64 builds. Both times, I'm
> checking this on an x86-64 machine.
>
> $ sparse --version
> v0.5.1-rc4-1-gfa71b7ac0594
>
> Is there something confusing to sparse in the GENMASK macro?
>
Hmm, it seems sparse is incorrectly taking ~0UL to be a 64-bit value
while BITS_PER_LONG is (correctly) evaluated to be 32.
#define GENMASK(h, l) \
(((~0UL) << (l)) & (~0UL >> (BITS_PER_LONG - 1 - (h))))
> --
> Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
> a Linux Foundation Collaborative Project
> --
> To unsubscribe from this list: send the line "unsubscribe linux-sparse" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2017-07-26 13:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-26 1:30 Sparse warnings on GENMASK + arm32 Stephen Boyd
2017-07-26 13:33 ` Lance Richardson [this message]
2017-07-26 13:46 ` Luc Van Oostenryck
2017-07-26 13:47 ` Christopher Li
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=1000702648.38599568.1501075981880.JavaMail.zimbra@redhat.com \
--to=lrichard@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sparse@vger.kernel.org \
--cc=sboyd@codeaurora.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