[OE-core] [PATCH] Revert "cross-canadian: Handle powerpc linux verses linux-gnuspe"
Khem Raj
raj.khem at gmail.com
Tue Jan 21 17:59:13 UTC 2014
On Saturday, January 18, 2014 11:20:07 AM Richard Purdie wrote:
> On Fri, 2014-01-17 at 14:43 +0000, alexandru.sardan at freescale.com wrote:
> > e500v1/v2 uses SPE to handle floating point operations
> > using general purpose regs.
> > So using the non-SPE compiler with SPE libraries won't work.
> > However the soft-fp libraries are compatible with the e500
> > ABI (with a considerable performance penalty).
> >
> > From what I can see, eglibc is built with SPE. So GCC should
> > be built also for SPE (target powerpc-poky-linux-gnuspe).
>
> The key question is this:
>
> Can one gcc binary generate code for both non-SPE and SPE targets,
> assuming its pointed at an appropriate sysroot containing appropriate
> libraries?
>
> If we can have one such binary, how do we configure it? If we can't, we
> need to redo the way gcc-cross-canadian is working on powerpc.
>
I think gcc can generate the code all you would need is option, real problem
is gcc runtime which will need different set of libraries and init files.
> The change there was to have one gcc for each different target
> architecture rather than each "tune" since that was horribly
> inefficient.
>
We dont need specific to tune but spe is ABI identifier that should be treated
differently then defaul tunes IMO
> Cheers,
>
> Richard
>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core at lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
--
-Khem
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20140121/b7c09919/attachment-0002.sig>
More information about the Openembedded-core
mailing list