README
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 817 f0b281498a86
child 1335 4a5540d3a301
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(+)
yann@1
     1
This is the README for crosstool-NG
yann@1
     2
yann@88
     3
To get you started, just enter:
yann@185
     4
  ./configure --help
yann@1
     5
yann@185
     6
You can find a (terse and WIP) documentation in docs/overview.txt.
yann@1
     7
yann@1
     8
You can also point your browser to
yann@88
     9
  http://ymorin.is-a-geek.org/dokuwiki/projects/crosstool
yann@96
    10
yann@185
    11
If you need to send a bug report or a patch, please send a mail with subject
yann@386
    12
prefixed with "[CT_NG]" with the following destinations:
yann@764
    13
    TO: yann.morin.1998 (at) anciens.enib.fr
yann@764
    14
    CC: crossgcc (at) sourceware.org
yann@386
    15
yann@386
    16
The people that helped are listed in docs/CREDITS. Many thanks to them! :-)
yann@185
    17
yann@908
    18
The list of known issues is listed in docs/known-issues.txt.
yann@817
    19
yann@185
    20
Aloha!