From: Christopher Li <sparse@chrisli.org>
To: Mike Frysinger <vapier@gentoo.org>
Cc: Josh Triplett <josh@joshtriplett.org>,
linux-sparse@vger.kernel.org, michael.hennerich@analog.com
Subject: Re: [PATCH] parser: add Blackfin gcc info
Date: Wed, 6 Oct 2010 14:14:07 -0700 [thread overview]
Message-ID: <AANLkTimp_cB4VgNH81xgDZ1ZGDLr_OhDse8LAUQMzdKB@mail.gmail.com> (raw)
In-Reply-To: <201010061232.51680.vapier@gentoo.org>
On Wed, Oct 6, 2010 at 9:32 AM, Mike Frysinger <vapier@gentoo.org> wrote:
> i guess sparse doesnt automatically propogate defines that gcc uses, so i'd
> have to add "-D__bfin__" to CHECKFLAGS in arch/blackfin/Makefile. but that is
> what people are expecting, right ?
Right. Same for __x86_64__, you need to tell sparse about it. I think
in the future
sparse should take the architecture arguments and define it automatically.
In other words, we should move some of the cgcc logic into sparse. But that
is for later change.
Chris
--
To unsubscribe from this list: send the line "unsubscribe linux-sparse" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-10-06 21:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-05 8:34 [PATCH] parser: add Blackfin gcc info Mike Frysinger
2010-10-05 16:18 ` Josh Triplett
2010-10-06 1:34 ` Mike Frysinger
2010-10-06 2:33 ` Christopher Li
2010-10-06 5:38 ` Mike Frysinger
2010-10-06 7:10 ` Josh Triplett
2010-10-06 8:40 ` Christopher Li
2010-10-06 14:52 ` Mike Frysinger
2010-10-06 16:32 ` Mike Frysinger
2010-10-06 21:14 ` Christopher Li [this message]
2010-10-06 7:05 ` Josh Triplett
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=AANLkTimp_cB4VgNH81xgDZ1ZGDLr_OhDse8LAUQMzdKB@mail.gmail.com \
--to=sparse@chrisli.org \
--cc=josh@joshtriplett.org \
--cc=linux-sparse@vger.kernel.org \
--cc=michael.hennerich@analog.com \
--cc=vapier@gentoo.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).