From: "H. Nikolaus Schaller" <hns@goldelico.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
PrasannaKumar Muralidharan <prasannatsmkumar@gmail.com>,
Mathieu Malaterre <malat@debian.org>,
Paul Cercueil <paul@crapouillou.net>
Subject: Re: linux-next: build warning after merge of the nvmem tree
Date: Fri, 6 Mar 2020 11:03:08 +0100 [thread overview]
Message-ID: <00D4DF40-E9A8-41AC-B1DA-4D656B6AC4F4@goldelico.com> (raw)
In-Reply-To: <20200306152827.6fe507bd@canb.auug.org.au>
Hi,
> Am 06.03.2020 um 05:28 schrieb Stephen Rothwell <sfr@canb.auug.org.au>:
>
> Hi all,
>
> After merging the nvmem tree, today's linux-next build (x86_64
> allmodconfig) produced this warning:
>
> In file included from include/linux/clk.h:13,
> from drivers/nvmem/jz4780-efuse.c:25:
> drivers/nvmem/jz4780-efuse.c: In function 'jz4780_efuse_read':
> include/linux/kernel.h:842:29: warning: comparison of distinct pointer types lacks a cast
> 842 | (!!(sizeof((typeof(x) *)1 == (typeof(y) *)1)))
> | ^~
> include/linux/kernel.h:856:4: note: in expansion of macro '__typecheck'
> 856 | (__typecheck(x, y) && __no_side_effects(x, y))
> | ^~~~~~~~~~~
> include/linux/kernel.h:866:24: note: in expansion of macro '__safe_cmp'
> 866 | __builtin_choose_expr(__safe_cmp(x, y), \
> | ^~~~~~~~~~
> include/linux/kernel.h:875:19: note: in expansion of macro '__careful_cmp'
> 875 | #define min(x, y) __careful_cmp(x, y, <)
> | ^~~~~~~~~~~~~
> drivers/nvmem/jz4780-efuse.c:76:24: note: in expansion of macro 'min'
> 76 | unsigned int chunk = min(bytes, (start + JZ_EFU_READ_SIZE)
> | ^~~
>
> Introduced by commit
>
> 50a09dfd394a ("nvmem: add driver for JZ4780 efuse")
The new kbuild robot message is more precise.
drivers/nvmem/jz4780-efuse.c:76:38: sparse: sparse: incompatible types in comparison expression (different type sizes):
drivers/nvmem/jz4780-efuse.c:76:38: sparse: unsigned long *
drivers/nvmem/jz4780-efuse.c:76:38: sparse: unsigned int *
A look into the code:
/* main entry point */
static int jz4780_efuse_read(void *context, unsigned int offset,
void *val, size_t bytes)
{
struct jz4780_efuse *efuse = context;
while (bytes > 0) {
unsigned int start = offset & ~(JZ_EFU_READ_SIZE - 1);
unsigned int chunk = min(bytes, (start + JZ_EFU_READ_SIZE)
- offset);
The problem seems to be that size_t is not always compatible to
unsigned int on all machines and compilers. My cross-gcc for MIPS
did not complain. kbuild robot tried for ARCH=x86_64 and in the
first warning for GCC_VERSION=7.5.0 make.cross ARCH=riscv
So I think we have to use
size_t start = offset & ~(JZ_EFU_READ_SIZE - 1);
size_t chunk = min(bytes, (start + JZ_EFU_READ_SIZE)
- offset);
I'l send a patch (after trying on MIPS).
BR and thanks,
Nikolaus
prev parent reply other threads:[~2020-03-06 10:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-06 4:28 Stephen Rothwell
2020-03-06 10:03 ` H. Nikolaus Schaller [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=00D4DF40-E9A8-41AC-B1DA-4D656B6AC4F4@goldelico.com \
--to=hns@goldelico.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=malat@debian.org \
--cc=paul@crapouillou.net \
--cc=prasannatsmkumar@gmail.com \
--cc=sfr@canb.auug.org.au \
--cc=srinivas.kandagatla@linaro.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
all inboxes | Powered by JetHome®