From: Josh Triplett <josh@freedesktop.org>
To: Pavel Roskin <proski@gnu.org>
Cc: linux-sparse@vger.kernel.org
Subject: Re: [PATCH 1/4] Compile sparse executable under it's own name, not as "check"
Date: Mon, 06 Nov 2006 10:50:00 -0800 [thread overview]
Message-ID: <454F83D8.9030204@freedesktop.org> (raw)
In-Reply-To: <20061103221659.7811.73832.stgit@dv.roinet.com>
[-- Attachment #1: Type: text/plain, Size: 736 bytes --]
I've applied this series of four patches; thanks.
Your "typo fixes" patch also reminded me that I needed to fix the typo in the
name of "validation/bad-assignement.c", which I have now done.
Regarding your comment about using "make check" for something more useful, I
would greatly welcome a patch which actually checked sparse against all the
files in validation/ and tested what those files intended to test. As far as
I can tell, it looks like some of them may not work as intended right now; for
example, it looks like validation/builtin_safe1.c expects
__attribute__((pure)) and __attribute__((const)) to work and mark a function
as side-effect-free, which doesn't currently happen in sparse.
- Josh Triplett
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
next prev parent reply other threads:[~2006-11-06 18:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-03 22:16 [PATCH 1/4] Compile sparse executable under it's own name, not as "check" Pavel Roskin
2006-11-03 22:17 ` [PATCH 2/4] Install cgcc on "make install", refactor installation code Pavel Roskin
2006-11-03 22:17 ` [PATCH 3/4] Add support for __builtin_strpbrk() Pavel Roskin
2006-11-03 22:17 ` [PATCH 4/4] Typo fixes Pavel Roskin
2006-11-06 18:50 ` Josh Triplett [this message]
2006-11-06 23:58 ` [PATCH 1/4] Compile sparse executable under it's own name, not as "check" Pavel Roskin
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=454F83D8.9030204@freedesktop.org \
--to=josh@freedesktop.org \
--cc=linux-sparse@vger.kernel.org \
--cc=proski@gnu.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.