config/arch/powerpc.in
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Tue Oct 14 17:42:10 2008 +0000 (2008-10-14)
changeset 929 7c958fb04f28
parent 898 fe3eda71a9d0
child 1181 2e88d85d6ffc
permissions -rw-r--r--
Sample config for e500v2 toolchain

On Tuesday 14 October 2008 17:05:31 Nate Case wrote:
> This is a sample config file for Freescale e500v2 processors (e.g.,
> MPC8548, MPC8572). It uses eglibc (for e500/SPE patches) and a recent
> gcc (4.3.1, for e500v2 DPFP support) and will generate appropriate
> dual-precision floating point instructions by default.
>
> Note: If building a Linux kernel with this toolchain, you will want to
> make sure -mno-spe AND -mspe=no are passed to gcc to prevent SPE
> ABI/instructions from getting into the kernel (which is currently
> unsupported). At this time, the kernel build system only passes
> -mno-spe by default (this should be fixed soon hopefully).
>
> A binutils snapshot is used to fix a bug present in 2.18 preventing
> U-Boot from being compiled (CodeSourcery issue #2297: internal.h
> (ELF_IS_SECTION_IN_SEGMENT): Adjust to cope with segments at the end of
> memory).

Obsoletes the powerpc-unknown-linux-gnuspe sample, so remove it.

/trunk/samples/powerpc-e500v2-linux-gnuspe/crosstool.config | 307 307 0 0 +++++++++++++++++++
1 file changed, 307 insertions(+)
     1 # powerpc specific configuration file
     2 
     3 config ARCH_powerpc
     4     select ARCH_SUPPORT_ABI
     5     select ARCH_SUPPORT_CPU
     6     select ARCH_SUPPORT_TUNE
     7     help
     8       The PowerPC architecture, as defined by:
     9         http://www.ibm.com/developerworks/eserver/articles/archguide.html
    10 
    11 config ARCH_POWERPC_SPE
    12     bool
    13     prompt "Enable SPE support"
    14     default n
    15     help
    16       Add support for the Signal Processing Engine.  This will set up
    17       the toolchain so that it supports the SPE ABI extensions. This
    18       mainly targets Freescale e500 processors.
    19 
    20       Setting this option will append "spe" to the end of your target
    21       tuple name (e.g., powerpc-e500v2-linux-gnuspe) so that the gcc
    22       configure/build system will know to include SPE ABI support.
    23       It will also automatically add "-mabi=spe -mspe" to your
    24       TARGET_CFLAGS, and "--enable-e500_double" to your CC_EXTRA_CONFIG,
    25       so you do not need to explicitly add them.