config/arch/powerpc.in
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Sun Jan 17 23:06:02 2010 +0100 (2010-01-17)
changeset 1740 c57458bb354d
parent 1345 27fec561af53
child 2112 0b83ab44a914
permissions -rw-r--r--
configure: do not require hg when configuring in an hg clone

When configuring in an hg clone, we need hg to compute the version string.
It can happen that users do not have Mercurial (eg. if they got a snapshot
rather that they did a full clone). In this case, we can still run, of
course, so simply fill the version string with a sufficiently explicit
value, that does not require hg. The date is a good candidate.
     1 # powerpc specific configuration file
     2 
     3 config ARCH_powerpc
     4     select ARCH_SUPPORTS_32
     5     select ARCH_SUPPORTS_64 if EXPERIMENTAL
     6     select ARCH_DEFAULT_32
     7     select ARCH_USE_MMU
     8     select ARCH_SUPPORT_ABI
     9     select ARCH_SUPPORT_CPU
    10     select ARCH_SUPPORT_TUNE
    11     help
    12       The PowerPC architecture, as defined by:
    13         http://www.ibm.com/developerworks/eserver/articles/archguide.html
    14 
    15 config ARCH_POWERPC_SPE
    16     bool
    17     prompt "Enable SPE support"
    18     default n
    19     help
    20       Add support for the Signal Processing Engine.  This will set up
    21       the toolchain so that it supports the SPE ABI extensions. This
    22       mainly targets Freescale e500 processors.
    23       
    24       Setting this option will append "spe" to the end of your target
    25       tuple name (e.g., powerpc-e500v2-linux-gnuspe) so that the gcc
    26       configure/build system will know to include SPE ABI support.
    27       It will also automatically add "-mabi=spe -mspe" to your
    28       TARGET_CFLAGS, and "--enable-e500_double" to your CC_EXTRA_CONFIG,
    29       so you do not need to explicitly add them.