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: Tue, 5 Oct 2010 19:33:21 -0700 [thread overview]
Message-ID: <AANLkTi=_MVVqr_hBx9GbhB5pmJWznakp8bmUXggfZAOi@mail.gmail.com> (raw)
In-Reply-To: <201010052134.42915.vapier@gentoo.org>
On Tue, Oct 5, 2010 at 6:34 PM, Mike Frysinger <vapier@gentoo.org> wrote:
>> I wonder, does it make sense to support these kinds of
>> architecture-specific builtins on all architectures, rather than
>> limiting them based on some specified target architecture?
>>
>> Since Sparse doesn't generate code, it can easily target all
>> architectures simultaneously, but that doesn't mean we couldn't tell it
>> what architecture to target. Sparse could default to targeting the
>> host architecture, which would avoid the need to pass extra flags in the
>> common case.
>
> it does sound like it'd be useful to add an arch command line option. but i
> hoped we could sneak in the Blackfin stuff first since other arches (like
> alpha) have been whitelisted.
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.
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 2:33 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 [this message]
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
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='AANLkTi=_MVVqr_hBx9GbhB5pmJWznakp8bmUXggfZAOi@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).