From: Christopher Li <sparse@chrisli.org>
To: Josh Triplett <josh@freedesktop.org>
Cc: Linux-Sparse <linux-sparse@vger.kernel.org>
Subject: Re: How do I get the latest sparse?
Date: Tue, 16 Jan 2007 22:31:47 -0800 [thread overview]
Message-ID: <20070117063147.GA2077@chrisli.org> (raw)
In-Reply-To: <45ADB71D.3080502@freedesktop.org>
On Tue, Jan 16, 2007 at 09:41:49PM -0800, Josh Triplett wrote:
> > Without cross function/file checking, the interrupt checking generates way
> > too many false positives.
>
> Sounds a lot like the context checking. :)
That is because the rules of the checking is too restrictive.
> The use of strcmp on asm strings for x86 instruction mnemonics seems like a
> problem, though.
Yes, I agree. The interrupt checking is an example of how the checker
can be written. It is not very usable as it is. I have a few idea to address
it, but it will not help the usability issue. Cross functions checking is the
way to go.
Chris
next prev parent reply other threads:[~2007-01-17 6:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-15 23:48 How do I get the latest sparse? Mitesh Shah
2007-01-16 0:17 ` Christopher Li
2007-01-16 12:23 ` Josh Triplett
2007-01-17 1:49 ` Christopher Li
2007-01-17 5:41 ` Josh Triplett
2007-01-17 6:31 ` Christopher Li [this message]
2007-01-17 19:05 ` Sam Ravnborg
2007-01-17 20:03 ` Christopher Li
2007-01-16 0:59 ` Randy Dunlap
2007-01-16 1:07 ` Mitesh Shah
2007-01-16 2:15 ` Randy Dunlap
2007-01-16 3:16 ` Dave Jones
2007-01-16 12:14 ` Josh Triplett
2007-01-16 15:40 ` Mitesh Shah
2007-01-17 0:23 ` Dave Jones
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=20070117063147.GA2077@chrisli.org \
--to=sparse@chrisli.org \
--cc=josh@freedesktop.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.