From: Christopher Li <sparse@chrisli.org>
To: linux-sparse@vger.kernel.org
Cc: Josh Triplett <josh@freedesktop.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [ANNOUNCE] sparse-0.2-cl1 is now available
Date: Sun, 4 Feb 2007 00:53:29 -0800 [thread overview]
Message-ID: <20070204085329.GA6520@chrisli.org> (raw)
Hi,
Thank Andrew for giving me some tips how the -mm series works.
I put together a series of patches I have been working on:
http://userweb.kernel.org/~chrisl/sparse-0.2-cl1/
Hopefully it will show up later at:
http://kernel.org/pub/linux/kernel/people/chrisl/sparse/sparse-0.2-cl1/
The most interesting part is the inline function annotation.
The new checker can find out inlined function usage. The interrupt
checker does not depend on x86 asm instruction any more.
Again, comment and feed back are always welcome.
Have a nice week end.
Chris
origin.patch
006eff06c7adcfb0d06c6fadf6e9b64f0488b2bf URL: git://git.kernel.org/pub/scm/linux/kernel/git/josh/sparse.git
sizeof-incomplete
Fix double semicolon in struct declare
debug-checker
Adding debug option for showing the linearized instruction.
no-dead-instruction
Disable liveness "dead" instruction by default.
anon-symbol
Fix core dump on anonymous symbol.
instruction-buffer-size
Fix core dump on huge switch
ptr-allocator
Make the ptrlist using the sparse allocator.
annotate-inline-2
Add annotation for inline function call.
show-call-symbol-addr
Show symbol address in calling.
malloc-checker
Adding the malloc NULL pointer checker.
interrupt-checker
Adding the interrupt checker
parse-attr
Free up some special bits in modifiers.
Total 12 patches
next reply other threads:[~2007-02-04 9:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-04 8:53 Christopher Li [this message]
2007-02-10 0:00 ` [ANNOUNCE] sparse-0.2-cl2 is now available Christopher Li
2007-02-10 17:33 ` Andi Kleen
2007-02-11 5:17 ` Christopher Li
2007-02-11 5:50 ` Al Viro
2007-02-11 6:02 ` Christopher Li
2007-02-11 10:41 ` Andi Kleen
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=20070204085329.GA6520@chrisli.org \
--to=sparse@chrisli.org \
--cc=akpm@linux-foundation.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.