From: Eric Sandeen <sandeen@redhat.com>
To: linux-xfs <linux-xfs@vger.kernel.org>
Subject: [PATCH 1/2] xfsprogs: enable sparse checking with make C=1
Date: Thu, 11 Oct 2018 11:12:52 -0500 [thread overview]
Message-ID: <97a4f428-9c9c-7bd7-7d6f-f2bf3a39b9ac@redhat.com> (raw)
In-Reply-To: <5b155482-78db-b58d-13d3-a478f79b1558@redhat.com>
Enable "make C=1" sparse checking when files get rebuilt. To check
all files, run "make clean" first.
This is a bit simpler than redefining CC for the whole build, which
requires extra commandline definitions and apparently is enough of a
barrier that nobody's doing sparse checking.
Note, this requires unreleased sparse after v0.5, which enables the
CHAR_BIT definition; otherwise it chokes.
Signed-off-by: Eric Sandeen <sandeen@redhat.com>
---
diff --git a/Makefile b/Makefile
index d031a60..05fe609 100644
--- a/Makefile
+++ b/Makefile
@@ -16,6 +16,20 @@ else
Q = @
endif
+CHECK=sparse
+CHECK_OPTS=-Wsparse-all -Wbitwise -Wno-transparent-union -Wno-return-void -Wno-undef \
+ -Wno-non-pointer-null -D__CHECK_ENDIAN__ -D__linux__
+
+ifeq ("$(origin C)", "command line")
+ ifeq ("$(C)", "1")
+ CHECK_CMD=$(CHECK) $(CHECK_OPTS)
+ else
+ CHECK_CMD=@true
+ endif
+endif
+
+export CHECK_CMD
+
MAKEOPTS = --no-print-directory Q=$(Q)
TOPDIR = .
diff --git a/doc/sparse.txt b/doc/sparse.txt
index 36a34a0..c6d1fe7 100644
--- a/doc/sparse.txt
+++ b/doc/sparse.txt
@@ -5,9 +5,18 @@ to check the source code of the open source XFS commands and utilites
First you need to install sparse, either from your distribution or from
source as provided at http://www.kernel.org/pub/software/devel/sparse/.
-To simply build the xfsprogs source code while checking the source using
-sparse just set the compiler to cgcc, which is a wrapper that calls both
-sparse and gcc using:
+The xfsprogs Makefile has a convenient shortcut to running sparse, by setting
+the C ("check") variable on the make commandline. To perform these checks on
+files when they get rebuilt, use:
+
+ make C=1
+
+(Note that xfsprogs does not yet support the kernel convention of checking
+all C files without compilation via "make C=2", so to run sparse on all
+C files, start with a "make clean")
+
+If you'd rather run sparse more manually, just set the compiler to cgcc,
+which is a wrapper that calls both sparse and gcc using:
CC=cgcc ./configure
diff --git a/include/buildrules b/include/buildrules
index c57fdfc..297e598 100644
--- a/include/buildrules
+++ b/include/buildrules
@@ -54,10 +54,13 @@ $(LTLIBRARY) : $(SUBDIRS) $(LTOBJECTS)
%.lo: %.c
@echo " [CC] $@"
$(Q)$(LTCOMPILE) -c $<
+ $(Q)$(CHECK_CMD) $(CFLAGS) $<
else
+
%.o: %.c
@echo " [CC] $@"
$(Q)$(CC) $(CFLAGS) -c $<
+ $(Q)$(CHECK_CMD) $(CFLAGS) $<
endif
next prev parent reply other threads:[~2018-10-11 23:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-11 16:10 [PATCH 0/2] xfsprogs: enable sparse checking with "make C=[12]" Eric Sandeen
2018-10-11 16:12 ` Eric Sandeen [this message]
2018-10-12 8:22 ` [PATCH 1/2] xfsprogs: enable sparse checking with make C=1 Carlos Maiolino
2018-10-14 17:08 ` Christoph Hellwig
2018-10-11 16:14 ` PATCH 2/2] xfsprogs: enable sparse checking with "make C=2" Eric Sandeen
2018-10-12 8:23 ` Carlos Maiolino
2018-10-14 17:09 ` Christoph Hellwig
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=97a4f428-9c9c-7bd7-7d6f-f2bf3a39b9ac@redhat.com \
--to=sandeen@redhat.com \
--cc=linux-xfs@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 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).