config/arch/powerpc.in.2
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Mon Mar 28 01:05:18 2011 +0200 (2011-03-28)
changeset 2362 0888065f8c4d
parent 1634 186c71e3ceb0
child 2467 200836977ce6
permissions -rw-r--r--
cc/gcc: cleanup the _or_later logic

So far, we've had a version always select appropriate _or_later option,
which in turn would select all previous _or_later options.

Because the dependencies on companion libs were cumulative, that was
working OK. But the upcoming 4.6 will no longer depend on libelf, so
we can't keep the cumulative scheme we've been using so far.

Have each release family select the corresponding dependencies, instead
of relying on selecting previous _or_later.

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.