From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: Christopher Li <sparse@chrisli.org>,
Dan Carpenter <dan.carpenter@oracle.com>,
smatch@vger.kernel.org
Cc: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Linux-Sparse <linux-sparse@vger.kernel.org>
Subject: Re: SMATCH indicates warning to almost all files in Linux Kernel + ARM
Date: Thu, 14 Sep 2017 19:33:56 +0200 [thread overview]
Message-ID: <CAExDi1QgpPJw1oAr=Q=myCTsgP+71EBU4=w5=3GiGAMsw3Tn9A@mail.gmail.com> (raw)
In-Reply-To: <CANeU7QmvVRtO6kddNwG0C8yv1+g=8tbcfqy9++Vy=wsDvH-rTQ@mail.gmail.com>
On Thu, Sep 14, 2017 at 5:55 PM, Christopher Li <sparse@chrisli.org> wrote:
> On Thu, Sep 14, 2017 at 3:01 AM, Kuninori Morimoto
> <kuninori.morimoto.gx@renesas.com> wrote:
>>
>> Hi Christopher
>>
>> I'm using SMATCH for Linux Kernel + ARM compile.
>> It indicates below warning for almost all files on ARM compile.
>> Thus, it is difficult to check "real" CHECK.
>> Is this my/kernel fault ?
>
> Adding linux sparse mailing list.
Adding Dan & smatch mailing list.
>> CC sound/soc/soc-dapm.o
>> CHK kernel/config_data.h
>> linux/arch/arm64/include/asm/lse.h:14:28: warning: Unknown escape 'l'
>> linux/arch/arm64/include/asm/lse.h:14:37: warning: Unknown escape 'l'
>> linux/arch/arm64/include/asm/alternative.h:172:28: warning: Unknown escape 'o'
>
> This is cause by the assembly syntax in arm header file.
>
>> ...
>> .macro alt_lse, llsc, lse
>> alternative_insn "\llsc", "\lse", ARM64_HAS_LSE_ATOMICS
>> .endm
This is solved in sparse since commit f83c2b8f0b5fcb8f60342b5a2fa51a84901f355a:
"warn on unknown escapes after preprocessing"
-- Luc Van Oostenryck
next parent reply other threads:[~2017-09-14 17:33 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 ` Luc Van Oostenryck [this message]
2017-09-15 1:29 ` SMATCH indicates warning to almost all files in Linux Kernel + ARM Kuninori Morimoto
2017-09-15 4:37 ` Luc Van Oostenryck
2017-09-15 5:41 ` Kuninori Morimoto
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='CAExDi1QgpPJw1oAr=Q=myCTsgP+71EBU4=w5=3GiGAMsw3Tn9A@mail.gmail.com' \
--to=luc.vanoostenryck@gmail.com \
--cc=dan.carpenter@oracle.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-sparse@vger.kernel.org \
--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).