From: Kamil Dudka <kdudka@redhat.com>
To: Christopher Li <sparse@chrisli.org>
Cc: Jeff Garzik <jeff@garzik.org>,
Sparse Mailing-list <linux-sparse@vger.kernel.org>
Subject: Re: [PATCH] compile-i386: do not generate an infinite loop
Date: Wed, 22 Jul 2009 19:21:58 +0200 [thread overview]
Message-ID: <200907221921.58947.kdudka@redhat.com> (raw)
In-Reply-To: <70318cbf0907220934p607b8c61g31fcec75e868d0d@mail.gmail.com>
On Wednesday 22 of July 2009 18:34:13 Christopher Li wrote:
> Just curious, what are you trying to build with sparse? A Linus filter
> would be pretty cool.
Sorry for my ignorance, I've never heard about the Linus filter. Could you
please point me to some relevant info? For now we only want to play with
separation logic and use it for static analysis of code as part of our
research at FIT BUT.
> BTW, I want to start some hacking guide for sparse. I am particular
> interested in what is the common pain when a new hacker try to work on
> sparse. Do you find sparse pretty easy to learn on?
I've just written my first "hello world" SPARSE client (nothing useful yet)
and I am going to write the same as gcc-4.5 plug-in and compare it with each
other - what is similar, what is different etc.
I haven't encountered any problem while learning SPARSE yet. The code is easy
to read and the examples sufficient. Maybe worth to write some brief
description of the particular examples within README? I'll come with some
ideas later if any.
Kamil
next prev parent reply other threads:[~2009-07-22 17:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-18 21:34 [PATCH] compile-i386: do not generate an infinite loop Kamil Dudka
2009-07-22 8:38 ` Christopher Li
2009-07-22 9:24 ` Kamil Dudka
2009-07-22 16:34 ` Christopher Li
2009-07-22 17:21 ` Kamil Dudka [this message]
2009-07-22 19:30 ` Christopher Li
2009-07-22 12:45 ` Jeff Garzik
2009-07-22 16:39 ` Christopher Li
2009-07-22 16:51 ` Jeff Garzik
2009-07-22 17:02 ` Kamil Dudka
2009-07-22 19:18 ` Christopher Li
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=200907221921.58947.kdudka@redhat.com \
--to=kdudka@redhat.com \
--cc=jeff@garzik.org \
--cc=linux-sparse@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 NNTP newsgroup(s).