Re: [PATCH] Revert "cross-canadian: Handle powerpc linux verses linux-gnuspe"

[Richard Purdie <richard.purdie@linuxfoundation.org>]

On Thu, 2014-01-23 at 18:22 +0000, alexandru.sardan@freescale.com wrote:
> > > Maybe I didn't understand correctly what kind of toolchain you want to
> > > be built in the end. Do you want to have a single GCC that builds all
> > > powerpc targets (e500v2, e5500, e6500 etc) and a separate sysroot for
> > each
> > > target?
> > 
> > Yes, this is exactly what is wanted. This is how the SDK is intended to
> > operate. The alternative and what we had before was a separate compiler
> > for each target which is rather wasteful.
> > 
> > > This may be problematic since, for example, the compiler that can
> > generate
> > > SPE (for e500v2) can't generate altivec instructions (for e6500).
> > 
> > Is there no way to configure gcc so it can generate for the different
> > targets assuming you pass in the right runtime target options?
> 
> [Alex Sardan] No. The more generic target powerpc-none-linux will not
> generate SPE code and the powerpc-none-linux-gnuspe target that generates
> SPE will not be able to generate Altivec.
> Maybe an exception can be added for e500v1/v2 targets so that a separate
> compiler can be generated for them? All the other targets will work fine
> with powerpc-none-linux using different runtime command line options.

An exception can probably be added (its all just software after all) but
the setup we have right now just allows for one compiler so some work
will be needed to make this work properly.

Cheers,

Richard