From: Kyle Moffett <mrmacman_g4@mac.com>
To: Al Viro <viro@ftp.linux.org.uk>
Cc: Hirokazu Takata <takata@linux-m32r.org>,
torvalds@odsl.org, linux-kernel@vger.kernel.org,
sam@ravnborg.org
Subject: Re: [PATCH] m32r: set CHECKFLAGS properly
Date: Tue, 27 Sep 2005 11:13:44 -0400 [thread overview]
Message-ID: <CFD86C0A-0BE4-4D39-BAAE-F985D997AFD2@mac.com> (raw)
In-Reply-To: <20050927071025.GS7992@ftp.linux.org.uk>
On Sep 27, 2005, at 03:10:25, Al Viro wrote:
> You do realize that this way sparse will get neither? It does not
> pick predefined symbols from gcc; thus the -D<your_arch>, etc.
How about sticking this in some global Makefile somewhere? This will
give sparse the same list of defines that GCC uses:
CHECKFLAGS += $(shell echo | gcc -E - -dM | sed -re 's/^#define +([^ ]
+) +(.*)$/-D\1=\2/g')
Or you could do this:
include/linux/checkerdefines.h:
echo | gcc -E - -dM >$@
And in linux/stddef.h or linux/compiler.h or something do:
#if defined(__CHECKER__) and not defined(_LINUX_CHECKERDEFINES_H)
# define _LINUX_CHECKERDEFINES_H 1
# include <linux/checkerdefines.h>
#endif
Cheers,
Kyle Moffett
--
Q: Why do programmers confuse Halloween and Christmas?
A: Because OCT 31 == DEC 25.
next prev parent reply other threads:[~2005-09-27 15:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-26 5:18 Al Viro
2005-09-27 6:13 ` Hirokazu Takata
2005-09-27 7:10 ` Al Viro
2005-09-27 15:13 ` Kyle Moffett [this message]
2005-09-27 16:34 ` Al Viro
2005-09-27 17:31 ` Kyle Moffett
2005-09-27 17:55 ` Al Viro
2005-09-27 18:37 ` Kyle Moffett
2005-09-27 23:06 ` Al Viro
2005-09-27 20:02 ` Sam Ravnborg
2005-09-28 1:44 ` Al Viro
2005-09-27 6:23 ` Hirokazu Takata
2005-09-27 15:00 ` Linus Torvalds
2005-09-28 0:18 ` Al Viro
2005-09-28 10:04 ` Hirokazu Takata
2005-09-29 1:56 ` Al Viro
2005-09-26 5:19 Al Viro
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=CFD86C0A-0BE4-4D39-BAAE-F985D997AFD2@mac.com \
--to=mrmacman_g4@mac.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=takata@linux-m32r.org \
--cc=torvalds@odsl.org \
--cc=viro@ftp.linux.org.uk \
/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
all inboxes | Powered by JetHome®