The IDE includes support for the Freescale e500 SPE. To use Freescale e500 SPE, you'll need to add the -me500v2 option to your compiler, linker, and assembler. However, once set, you won't be able to include regular PPC binaries with the ones for which you specified the -me500v2 option. In addition, for your older legacy binaries, you won't be able to take advantage of SPE.
The e500 PPC core contains an SPE unit, that has a FPU that is different from the classic PPC FPU. The QNX kernel supports the SPE registers, and the Command Line tools are able to generate SPE code by supporting the compiler, assembler, and linker. In addition, the libraries — in particular the libm library — were rebuilt because of the change in the ABI (because e500 doesn't have fp registers, so it needs a new ABI; no compiler with the classic PowerPC ABI will work for e500.)
From the command line, to build for SPE, you'll need to specify the following command:
qcc -Vgcc_ntoppcbe -me500v2
After adding new conf files, you'll need to specify the following command:
qcc -Vgcc_ntoppcbespe
By default, the qcc -Vgcc_ntoppcbespe has the -me500v2 option enabled.
If either you, or the IDE, creates a o-be-spe or o.be.spe variant directory, the Makefiles will add the -me500v2 option to CCOPTS, ASOPTS, and LDOPTS, which will then be passed to the compiler, assembler, and linker, thereby enabling support for Freescale e500 SPE.
For debug, nothing is required; SPE information is retrieved from the binary.
In the IDE, to create a new target with Freescale e500 SPE support, do the following:
The compiler, assembler, and linker will automatically be enabled for Freescale e500 SPE.