linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Dan Carpenter" <error27@gmail.com>
To: Michael Stefaniuc <mstefani@redhat.com>
Cc: smatch-discuss@lists.sourceforge.net, linux-sparse@vger.kernel.org
Subject: Re: Moving smatch to use sparse
Date: Thu, 5 Oct 2006 13:58:02 -0700	[thread overview]
Message-ID: <a63d67fe0610051358j6181f558p2baaf1b59b0a042e@mail.gmail.com> (raw)
In-Reply-To: <45252A39.3050008@redhat.com>

On 10/5/06, Michael Stefaniuc <mstefani@redhat.com> wrote:
> Hello Dan,
>
> Dan Carpenter wrote:
> > Work on smatch is going ahead.  I have one real life check is working
> > and I've added a patched up the core code quite a bit.
> great work! What about the old smatch.pm and perl scripts? Will i be
> still able to use those or would i have to port them over? I'm still
> using the old smatch on checking Wine.
>
> bye
>         michael
>

They'll have to be ported I'm afraid.

Rewrites are a pain, but it's worth it because now it's easier to
install, it's easier to use, and it runs a bajillion times faster.
Using sparse also buys us a bunch of features for free, for example if
you have 'i' defined in two different scopes with sparse handles that.
 Another example is compound conditions.  The old code was confused by
stuff like:
if (a && a->foo() || a && a->bar())
there wasn't a good way to deal with that with the old way.

Which checks do you use most?  I'll port those first...

regards,
dan carpenter

  reply	other threads:[~2006-10-05 20:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <a63d67fe0607140925h3665cd98ibc2fab07f6f80360@mail.gmail.com>
2006-07-16  0:42 ` Moving smatch to use sparse Dan Carpenter
2006-10-05  8:41   ` Dan Carpenter
2006-10-05  9:26     ` Sam Ravnborg
2006-10-05  9:49       ` Dan Carpenter
2006-10-05 10:25         ` Jörn Engel
2006-10-06  6:31           ` Dan Carpenter
2006-10-05 15:52     ` Michael Stefaniuc
2006-10-05 20:58       ` Dan Carpenter [this message]
2006-10-05 22:46         ` Michael Stefaniuc
2006-10-06  8:57           ` 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=a63d67fe0610051358j6181f558p2baaf1b59b0a042e@mail.gmail.com \
    --to=error27@gmail.com \
    --cc=linux-sparse@vger.kernel.org \
    --cc=mstefani@redhat.com \
    --cc=smatch-discuss@lists.sourceforge.net \
    /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).