From: Pekka Enberg <penberg@kernel.org>
To: linux-sparse@vger.kernel.org
Cc: Pekka Enberg <penberg@kernel.org>,
Christopher Li <sparse@chrisli.org>,
Jeff Garzik <jgarzik@redhat.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: [PATCH 2/3] sparse, llvm: Add test case for <stdbool.h> type
Date: Wed, 21 Dec 2011 11:25:27 +0200 [thread overview]
Message-ID: <1324459528-9344-2-git-send-email-penberg@kernel.org> (raw)
In-Reply-To: <1324459528-9344-1-git-send-email-penberg@kernel.org>
As it turns out, our validation test harness doesn't catch <stdbool.h> related
breakage so add a minimal test case that does.
Cc: Christopher Li <sparse@chrisli.org>
Cc: Jeff Garzik <jgarzik@redhat.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Signed-off-by: Pekka Enberg <penberg@kernel.org>
---
validation/backend/bool-test.c | 11 +++++++++++
1 files changed, 11 insertions(+), 0 deletions(-)
create mode 100644 validation/backend/bool-test.c
diff --git a/validation/backend/bool-test.c b/validation/backend/bool-test.c
new file mode 100644
index 0000000..51ae356
--- /dev/null
+++ b/validation/backend/bool-test.c
@@ -0,0 +1,11 @@
+#include <stdbool.h>
+
+static bool return_false(void)
+{
+ return false;
+}
+
+/*
+ * check-name: Boolean type code generation
+ * check-command: ./sparsec -c $file -o tmp.o
+ */
--
1.7.6.4
next prev parent reply other threads:[~2011-12-21 9:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-21 9:25 [PATCH 1/3] sparse, llvm: Use LLVMInt1Type() in sym_basetype_type() Pekka Enberg
2011-12-21 9:25 ` Pekka Enberg [this message]
2011-12-21 9:58 ` [PATCH 2/3] sparse, llvm: Add test case for <stdbool.h> type Josh Triplett
2011-12-21 10:18 ` Pekka Enberg
2011-12-22 0:23 ` Christopher Li
2011-12-22 5:53 ` Pekka Enberg
2011-12-21 9:25 ` [PATCH 3/3] Revert "sparse: Bump up sizeof(_Bool) to 8 bits" Pekka Enberg
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=1324459528-9344-2-git-send-email-penberg@kernel.org \
--to=penberg@kernel.org \
--cc=jgarzik@redhat.com \
--cc=linux-sparse@vger.kernel.org \
--cc=sparse@chrisli.org \
--cc=torvalds@linux-foundation.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 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).