config/arch/powerpc.in.2
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Sun Mar 20 00:02:21 2011 +0100 (2011-03-20)
changeset 2339 730e2d63296b
parent 1634 186c71e3ceb0
child 2467 200836977ce6
permissions -rw-r--r--
scripts: leave changelog in build dir, copy to install dir

Users tend to look for the build log in the current working directory,
rather than in the toolchain's installation dir. While bundling the build
log in the toolchain installation dir is nice for distribution and review,
it can be easier to have the build log readily available in the working
directory, as it is quicker to get to it.

So, the build log stays in the working directory until the toolchain is
completely and successfully built, and then a (compressed) copy is made.

Reported-by: Trevor Woerner <twoerner@gmail.com>
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.