From: Josh Triplett <josh@freedesktop.org>
To: linux-sparse@vger.kernel.org
Subject: [ANNOUNCE] Sparse 0.2 released
Date: Tue, 05 Dec 2006 04:20:38 -0800 [thread overview]
Message-ID: <45756416.3020800@freedesktop.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1796 bytes --]
I have tagged and tarballed a 0.2 release of Sparse, now available from
<http://kernel.org/pub/linux/kernel/people/josh/sparse/dist/sparse-0.2.tar.gz>,
with sha1sum `1762fc609fe436e74b87356a52690b5f7bb40c81`.
In addition to plenty of bug fixes, this release includes several notable new
features:
* -Wall, thanks to Pavel Roskin
* `#strong_define` and `#strong_undef`, thanks to Oleg Nesterov
* Argument parsing functions no longer mangle the argv passed to them, thanks
to Christopher Li
* static library and header files now installed, along with a pkg-config file
to find them
* Makefile now supports DESTDIR, useful for packagers
Full changelog:
Christopher Li (4):
trivial fix for seg fault.
Fix warning on self check.
delay removing file scope
cleanup write to argument array hack
Damien Lespiau (1):
trivial: more .gitignore stuff
Josh Triplett (5):
Update the FAQ: add sparse website and gitweb, update git URL, remove old BK url
Rename "check.c" to "sparse.c" to match program name; update .gitignore
Install static library and header files
Generate and install a pkg-config file. Add DESTDIR support to Makefile.
Remove old SCCS target from Makefile.
Nicolas Kaiser (1):
double inclusions
Oleg Nesterov (7):
use lookup_macro() in handle_undef()
kill NS_INVISIBLEMACRO, introduce NS_UNDEF
fix redefine of #weak_define
fix 'weak' attribute loss
prepare for #strong_{define,undef}
implement #strong_define
implement #strong_undef
Pavel Roskin (1):
Support -Wall flag
-- Josh Triplett
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
reply other threads:[~2006-12-05 12:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=45756416.3020800@freedesktop.org \
--to=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.