From: Sam Ravnborg <sam@ravnborg.org>
To: Al Viro <viro@ftp.linux.org.uk>
Cc: Hirokazu Takata <takata@linux-m32r.org>,
torvalds@odsl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] m32r: set CHECKFLAGS properly
Date: Tue, 27 Sep 2005 22:02:30 +0200 [thread overview]
Message-ID: <20050927200230.GA8403@mars.ravnborg.org> (raw)
In-Reply-To: <20050927071025.GS7992@ftp.linux.org.uk>
> Sam, any help in that area? Ideally we want to have something equivalent
> to
> PREDEFINED_WE_MIGHT_WANT = __m32r__ __LITTLE_ENDIAN__ __BIG_ENDIAN__
> and CHECKFLAGS done from that - basically, the subset of cross-gcc
> predefined symbols reproduced for sparse. Ideally with -m64 added
> if we have sizeof(long) == 8 on target, to take care of all that
> crap in one go.
>
> Suggestions?
The most simple solution would be to provide a small script that
create the defines as we need and run it for each invocation of sparse.
The script should use same trick as scripts/gcc-version.sh does.
So we could have:
#!/bin/sh
compiler="$*"
BIG=$(echo __BIG_ENDIAN__ | $compiler -E -xc - | tail -n 1)
LITTLE=$(echo __LITTLE_ENDIAN__ | $compiler -E -xc - | tail -n 1)
Then BIG would be set to "1" if this is big endian, and "__BIG_ENDIAN__"
if little endian.
A little bit of shell script and we have the defines we want for m32r.
Then we could add calling this script as part of sparse invocation.
The better solution would be to find the relevant flags before we
start building the kernel. This is not so easy if we want access to
final CFLAGS. But for the architecture the important ones are
defined in arch/Makefile so placing this late in the file and
use $(CC) $(CFLAGS) should be OK in almost all cases.
Too late for me to cook up a patch right now - but simple.
Oh, and I agree. We do NOT want all the gcc defined flags.
We should restrict to a subset in the kernel - so it's good
if sparse warns/errors out on usage of the non-trivial defines.
Sam
next prev parent reply other threads:[~2005-09-27 20:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-26 5:18 [PATCH] m32r: set CHECKFLAGS properly Al Viro
2005-09-27 6:13 ` Hirokazu Takata
2005-09-27 7:10 ` Al Viro
2005-09-27 15:13 ` Kyle Moffett
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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
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=20050927200230.GA8403@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=linux-kernel@vger.kernel.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