linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kbuild <linux-kbuild@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	smatch@vger.kernel.org
Subject: Re: sparse on scripts/kconfig/*.c
Date: Wed, 10 May 2017 23:53:57 +0300	[thread overview]
Message-ID: <20170510205357.xshdaack6mwku5np@mwanda> (raw)
In-Reply-To: <20170510101838.c5nwzaraeybyypwj@mwanda>

I have created some new tools to make this process easier.

1) First you still have to edit the Makefile:

-HOSTCC       = gcc
+HOSTCC       = ~/progs/smatch/devel/cgcc

2) Build the data with this command:

	~/progs/smatch/devel/smatch_scripts/build_generic_data.sh --target scripts/

The --target scripts/ is because we want to run smatch on the scripts/
directory.

3) Run smatch:

	~/progs/smatch/devel/smatch_scripts/test_generic.sh --target scripts/

I just wrote this code today so it might be a bit rough perhaps.  Let me
know if you have any issues.  It doesn't find anything like I said
before, but hopefully this can help other people who want to run Smatch
on user space code.

regards,
dan carpenter

  reply	other threads:[~2017-05-10 20:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-09 16:47 sparse on scripts/kconfig/*.c Randy Dunlap
2017-05-09 20:17 ` Christoph Hellwig
2017-05-10  0:27   ` Randy Dunlap
2017-05-10  7:28     ` Christoph Hellwig
2017-05-10 16:42       ` Randy Dunlap
2017-05-10 10:18 ` Dan Carpenter
2017-05-10 20:53   ` Dan Carpenter [this message]
2017-05-15 18:00     ` Randy Dunlap
2017-05-16  9:43       ` Dan Carpenter
2017-05-18  2:53         ` Randy Dunlap
2017-05-18  7:14           ` Dan Carpenter

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=20170510205357.xshdaack6mwku5np@mwanda \
    --to=dan.carpenter@oracle.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=smatch@vger.kernel.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 NNTP newsgroup(s).