From: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
To: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Cc: Christopher Li <sparse@chrisli.org>,
Dan Carpenter <dan.carpenter@oracle.com>,
smatch@vger.kernel.org,
Linux-Sparse <linux-sparse@vger.kernel.org>
Subject: Re: SMATCH indicates warning to almost all files in Linux Kernel + ARM
Date: Fri, 15 Sep 2017 05:41:41 +0000 [thread overview]
Message-ID: <8760ckttif.wl%kuninori.morimoto.gx@renesas.com> (raw)
In-Reply-To: <CAExDi1Rgdtb5T5HZZwD+-=EwALkfLOEkVWHattfPALbphZ4v5Q@mail.gmail.com>
Hi Luc
> > I tried variously things, and it seems smatch doesn't check #if ?
> > This lse.h file is this construction.
> >
> > --- lse.h ----------
> > ...
> > #if defined(CONFIG_AS_LSE) && defined(CONFIG_ARM64_LSE_ATOMICS)
>
> I'm sure that smatch does check #if, but the wrong warnings you saw about the
> escaped 'l' & 'o' are issued during tokenization, before the
> pre-processing took place.
> So using #ifdef __ASSEMBLER or anything using pre-processing won't help you.
> The commit I gave here above is really needed.
OK, thank you for your help.
I'm looking forward to use your patch
Best regards
---
Kuninori Morimoto
prev parent reply other threads:[~2017-09-15 5:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8760clkby1.wl%kuninori.morimoto.gx@renesas.com>
[not found] ` <CANeU7QmvVRtO6kddNwG0C8yv1+g=8tbcfqy9++Vy=wsDvH-rTQ@mail.gmail.com>
2017-09-14 17:33 ` SMATCH indicates warning to almost all files in Linux Kernel + ARM Luc Van Oostenryck
2017-09-15 1:29 ` Kuninori Morimoto
2017-09-15 4:37 ` Luc Van Oostenryck
2017-09-15 5:41 ` Kuninori Morimoto [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=8760ckttif.wl%kuninori.morimoto.gx@renesas.com \
--to=kuninori.morimoto.gx@renesas.com \
--cc=dan.carpenter@oracle.com \
--cc=linux-sparse@vger.kernel.org \
--cc=luc.vanoostenryck@gmail.com \
--cc=smatch@vger.kernel.org \
--cc=sparse@chrisli.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).