linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Josh Triplett <josh@joshtriplett.org>
To: Mike Frysinger <vapier@gentoo.org>
Cc: linux-sparse@vger.kernel.org, michael.hennerich@analog.com
Subject: Re: [PATCH] parser: add Blackfin gcc info
Date: Tue, 5 Oct 2010 09:18:30 -0700	[thread overview]
Message-ID: <20101005161829.GB1859@feather> (raw)
In-Reply-To: <1286267670-20974-1-git-send-email-vapier@gentoo.org>

On Tue, Oct 05, 2010 at 04:34:30AM -0400, Mike Frysinger wrote:
> The Blackfin port uses some custom attributes to control memory placement,
> and it has some custom builtins.  So add the ones that the kernel actually
> utilizes to avoid massive build errors with sparse.
> 
> Signed-off-by: Mike Frysinger <vapier@gentoo.org>

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.

- Josh Triplett

  reply	other threads:[~2010-10-05 16:19 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 [this message]
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
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=20101005161829.GB1859@feather \
    --to=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).