From: Nathan Chancellor <natechancellor@gmail.com>
To: Phong Tran <tranmanphong@gmail.com>
Cc: robh+dt@kernel.org, frowand.list@gmail.com,
pantelis.antoniou@konsulko.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Nick Desaulniers <ndesaulniers@google.com>,
clang-built-linux@googlegroups.com
Subject: Re: [PATCH] of: replace be32_to_cpu to be32_to_cpup
Date: Tue, 30 Apr 2019 02:37:49 -0700 [thread overview]
Message-ID: <20190430093749.GA29126@archlinux-i9> (raw)
In-Reply-To: <20190430090044.16345-1-tranmanphong@gmail.com>
+ Nick and the list
On Tue, Apr 30, 2019 at 04:00:44PM +0700, Phong Tran wrote:
> The cell is a pointer to __be32.
> with the be32_to_cpu a lot of clang warning show that:
>
> ./include/linux/of.h:238:37: warning: multiple unsequenced modifications
> to 'cell' [-Wunsequenced]
> r = (r << 32) | be32_to_cpu(*(cell++));
> ^~
> ./include/linux/byteorder/generic.h:95:21: note: expanded from macro
> 'be32_to_cpu'
> ^
> ./include/uapi/linux/byteorder/little_endian.h:40:59: note: expanded
> from macro '__be32_to_cpu'
> ^
> ./include/uapi/linux/swab.h:118:21: note: expanded from macro '__swab32'
> ___constant_swab32(x) : \
> ^
> ./include/uapi/linux/swab.h:18:12: note: expanded from macro
> '___constant_swab32'
> (((__u32)(x) & (__u32)0x000000ffUL) << 24) | \
> ^
>
> Signed-off-by: Phong Tran <tranmanphong@gmail.com>
> ---
> include/linux/of.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/linux/of.h b/include/linux/of.h
> index e240992e5cb6..1c35fc8f19b0 100644
> --- a/include/linux/of.h
> +++ b/include/linux/of.h
> @@ -235,7 +235,7 @@ static inline u64 of_read_number(const __be32 *cell, int size)
> {
> u64 r = 0;
> while (size--)
> - r = (r << 32) | be32_to_cpu(*(cell++));
> + r = (r << 32) | be32_to_cpup(cell++);
> return r;
> }
>
> --
> 2.21.0
>
While the patch does remove the warning, I am not convinced that this
isn't a clang bug based on my brief analysis here:
https://github.com/ClangBuiltLinux/linux/issues/460#issuecomment-487808008
However, I'm waiting for people smarter than I am to comment on whether
that sounds correct or not.
I am not familiar with the various different big/little endian functions
enough to review this but thank you for the patch!
Nathan
next prev parent reply other threads:[~2019-04-30 9:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-30 9:00 [PATCH] of: replace be32_to_cpu to be32_to_cpup Phong Tran
2019-04-30 9:37 ` Nathan Chancellor [this message]
2019-04-30 10:52 ` David Laight
2019-04-30 14:56 ` [PATCH V2] of: fix clang -Wunsequenced for be32_to_cpu() Phong Tran
2019-04-30 16:28 ` Nick Desaulniers
2019-04-30 16:29 ` Nick Desaulniers
2019-05-01 18:13 ` Nick Desaulniers
2019-05-01 19:33 ` Rob Herring
2019-04-30 13:32 ` [PATCH] of: replace be32_to_cpu to be32_to_cpup Christoph Hellwig
2019-04-30 14:44 ` Phong Tran
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=20190430093749.GA29126@archlinux-i9 \
--to=natechancellor@gmail.com \
--cc=clang-built-linux@googlegroups.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ndesaulniers@google.com \
--cc=pantelis.antoniou@konsulko.com \
--cc=robh+dt@kernel.org \
--cc=tranmanphong@gmail.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).