Re: [PATCH] parser: add Blackfin gcc info

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


On Tue, Oct 05, 2010 at 09:34:41PM -0400, Mike Frysinger wrote:
> On Tuesday, October 05, 2010 12:18:30 Josh Triplett wrote:
> > 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.
> > 
> > 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.

Absolutely.  I took the opportunity to raise the general problem, but
that doesn't mean that Blackfin should have to wait for the general
solution. :)

- Josh Triplett
--
To unsubscribe from this list: send the line "unsubscribe linux-sparse" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Newbies FAQ]     [Kernel List]     [Site Home]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [Bugtraq]     [Photo]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [DDR & Rambus]     [Trinity Fuzzer Tool]

Powered by Linux