config/arch/powerpc.in.2
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Thu Dec 23 20:43:32 2010 +0100 (2010-12-23)
changeset 2307 2efd46963086
parent 1634 186c71e3ceb0
child 2467 200836977ce6
permissions -rw-r--r--
buildtools: move to working directory

There is absolutely *no* reason for the buildtools (wrappers to gcc, g++,
as, ld... for the local machine) to be in the toolchain directory. Moreover,
they are removed after the build completes.

Move them out of the toolchain directory, and into the build directory (but
yet the part specific to the current toolchain). This means we no longer
need to explicitly remove them either, BTW, but we need to save/restore them
for the restart feature.

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
yann@520
     1
# powerpc specific configuration file
yann@628
     2
yann@1634
     3
config ARCH_POWERPC_SPE
yann@1634
     4
    bool
yann@1634
     5
    prompt "Enable SPE support"
yann@1634
     6
    default n
yann@1634
     7
    help
yann@1634
     8
      Add support for the Signal Processing Engine.  This will set up
yann@1634
     9
      the toolchain so that it supports the SPE ABI extensions. This
yann@1634
    10
      mainly targets Freescale e500 processors.
yann@1634
    11
      
yann@1634
    12
      Setting this option will append "spe" to the end of your target
yann@1634
    13
      tuple name (e.g., powerpc-e500v2-linux-gnuspe) so that the gcc
yann@1634
    14
      configure/build system will know to include SPE ABI support.
yann@1634
    15
      It will also automatically add "-mabi=spe -mspe" to your
yann@1634
    16
      TARGET_CFLAGS, and "--enable-e500_double" to your CC_EXTRA_CONFIG,
yann@1634
    17
      so you do not need to explicitly add them.