Hi,
I'm running into a build problem when building GCC 6.1.0:
/home/patrick/src/e7/toolchain/build/gcc-6.1.0-stage2/./gcc/xgcc
-shared-libgcc
-B/home/patrick/src/e7/toolchain/build/gcc-6.1.0-stage2/./gcc
-nostdinc++
-L/home/patrick/src/e7/toolchain/build/gcc-6.1.0-stage2/powerpc-eabispe/lib
Hi,
I've recently been using a target (e200z6) where a "-mno-spe
-mabi=no-spe" libgcc was required.
The closest combination provided by 4.9.1 was "-mno-spe -mabi=no-spe
-mno-isel". My builds disable spe, but leave isel enabled.
Unfortunately, with this combination of options gcc uses an inco
On 15/02/17 01:49, Segher Boessenkool wrote:
It is also used in many PPC based microcontrollers, which are used in
the automotive industry and other places where you need highly reliable
and robust but powerful microcontrollers. However, gcc support for
these has traditionally been poor - there
On 15/02/17 01:49, Segher Boessenkool wrote:
With the Qualcomm takeover of Freescale/NXP I guess the PowerPC has no
future in this area and they will move to ARM for the processor cores.
That is my understanding as well, yes.
Our reps have suggested that the opposite may well be the case: It
