From: Randy Dunlap <rdunlap@xenotime.net>
To: Mish Mash <khalota@gmail.com>
Cc: linux-sparse@vger.kernel.org
Subject: Re: looking for any examples of using sparse
Date: Sat, 28 Jul 2007 10:44:14 -0700 [thread overview]
Message-ID: <20070728104414.ff81537a.rdunlap@xenotime.net> (raw)
In-Reply-To: <bb2368c50705090732w4948fcc0ka3aea74ba22945b5@mail.gmail.com>
On Wed, 9 May 2007 16:32:30 +0200 Mish Mash wrote:
> dear all,
>
> I'm trying to use sparse for writing various source code analysis
> tools (I was using ctool previously). I'm currently going through the
> source trying to figure out what I need. Given the excessive amounts
> of comments I'm having to wade through, this probably isn't the
> fastest way of figuring the beast out ;)
>
> Does anyone have any notes they've taken or can point me at code that
> uses sparse to help get a rough idea of how to use the beast? (Ideally
> slightly more detailed than Randy Dunlap's howto) I noticed smatch now
> uses sparse and i've applied their patch which I'm going over. Is
> there anything better? (I've already found the no longer very useful
> presentation at http://developer.osdl.org/dmo/sparse/)
[belated]
Hi,
My sparse howto was never meant to be a guide to sparse internals,
but agreed, something like that would be very helpful.
My sparse howto is really intended to be a basic/intro user guide since
I didn't find one anywhere else. And I have just updated it --
comments/corrections welcome.
http://www.xenotime.net/linux/sparse/sparse_howto.txt
---
~Randy
prev parent reply other threads:[~2007-07-28 17:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-09 14:32 looking for any examples of using sparse Mish Mash
2007-05-10 6:34 ` Mike Goodwin
2007-05-10 17:46 ` A Sparse C Interpreter [was: looking for any examples of using sparse] Tommy Thorn
2007-07-28 17:44 ` Randy Dunlap [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=20070728104414.ff81537a.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=khalota@gmail.com \
--cc=linux-sparse@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).