From: Yoshinori Sato <ysato@users.sourceforge.jp>
To: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Cc: uclinux-h8-devel@lists.sourceforge.jp, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] h8300:let the checker know that size_t is ulong
Date: Sun, 22 Jul 2018 23:02:31 +0900 [thread overview]
Message-ID: <87h8krfjwo.wl-ysato@users.sourceforge.jp> (raw)
In-Reply-To: <20180530210343.22320-1-luc.vanoostenryck@gmail.com>
On Thu, 31 May 2018 06:03:43 +0900,
Luc Van Oostenryck wrote:
>
> All 64bit archs use unsigned long for size_t and most 32bit
> archs use 'unsigned int'. By default, this is what is assumed
> by sparse.
>
> However, on h8300 (a 32bit arch) size_t is unsigned long which
> can led sparse to emit wrong warnings.
>
> Fix this by passing to sparse the flag -msize-long, telling it
> that size_t is unsigned long.
>
> Signed-off-by: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
> ---
> arch/h8300/Makefile | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/arch/h8300/Makefile b/arch/h8300/Makefile
> index e1c02ca23..eaac6685f 100644
> --- a/arch/h8300/Makefile
> +++ b/arch/h8300/Makefile
> @@ -22,6 +22,8 @@ KBUILD_CFLAGS += -DUTS_SYSNAME=\"uClinux\"
> KBUILD_AFLAGS += $(aflags-y)
> LDFLAGS += $(ldflags-y)
>
> +CHECKFLAGS += -msize-long
> +
> ifeq ($(CROSS_COMPILE),)
> CROSS_COMPILE := h8300-unknown-linux-
> endif
> --
> 2.17.0
>
Sorry too late replay.
Applied to h8300-next.
Thanks.
--
Yosinori Sato
prev parent reply other threads:[~2018-07-22 14:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-30 21:03 [PATCH] h8300:let the checker know that size_t is ulong Luc Van Oostenryck
2018-07-22 14:02 ` Yoshinori Sato [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=87h8krfjwo.wl-ysato@users.sourceforge.jp \
--to=ysato@users.sourceforge.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=luc.vanoostenryck@gmail.com \
--cc=uclinux-h8-devel@lists.sourceforge.jp \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.