From: Mike Frysinger <vapier@gentoo.org>
To: Christopher Li <sparse@chrisli.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 10:52:49 -0400 [thread overview]
Message-ID: <201010061052.50958.vapier@gentoo.org> (raw)
In-Reply-To: <AANLkTim=hG4BQ2fxy-_LKR1z-NZOqJYffaOJw+0yJvYK@mail.gmail.com>
[-- Attachment #1: Type: Text/Plain, Size: 1847 bytes --]
On Wednesday, October 06, 2010 04:40:09 Christopher Li wrote:
> On Wed, Oct 6, 2010 at 12:10 AM, Josh Triplett wrote:
> >> > Can we have some "ifdef" for the blackfin architecture in the pre
> >> > buffer? I agree with Josh, that do look like very much blackfin
> >> > specific. We can leave the ignore attribute alone for now.
> >>
> >> how would #ifdefs help ? i'm not building sparse for a Blackfin arch,
> >> host or target wise. if there's something more, you'd have to be
> >> specific as to what you mean, otherwise i wont be able to send an
> >> updated patch.
> >
> > I suspect that Chris meant that you could add_pre_buffer an #ifdef and
> > #endif surrounding the #define, so that the #define would only take
> > effect if Sparse (or the command-line options passed by cgcc or Linux)
> > defined some appropriate architecture-specific symbol for Blackfin.
>
> Thanks for the clarification. The pre buffer is just a build in piece of
> the header file. You can still use #ifdef inside the pre buffer. I just
> don't want those blackfin specific declare show up in every other platform
>
> >> yes, these things are completely Blackfin specific, but i dont see how
> >> that's a barrier for entry when both attributes and the builtin ignore
> >> lists contain completely architecture specific stuff without any #ifdef
> >> logic. using sparse on the Linux kernel for the Blackfin port is
> >> pretty useless atm because of these missing pieces.
>
> No, I don't mean that is a deal breaker. That is some thing nice to have.
> Do you know any typical architecture defined symbol to identify the
> blackfin port? Some thing similar to __x86_64__. How does gcc know it is
> compiling for a Blackfin port?
Blackfin's gcc always outputs __bfin__. i'll send an updated patch once i
test it out.
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2010-10-06 14:54 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 [this message]
2010-10-06 16:32 ` Mike Frysinger
2010-10-06 21:14 ` Christopher Li
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=201010061052.50958.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=josh@joshtriplett.org \
--cc=linux-sparse@vger.kernel.org \
--cc=michael.hennerich@analog.com \
--cc=sparse@chrisli.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.