samples/powerpc-e500v2-linux-gnuspe/reported.by
author "Yann E. MORIN" <yann.morin.1998@free.fr>
Sun May 11 23:43:52 2014 +0200 (2014-05-11)
changeset 3320 78af1c99bc6d
parent 2290 ba82eb173bd4
permissions -rw-r--r--
scripts/functions: add target_endian_le and target_endian_be

We currently define target_endian_el and target_endian_eb to be the
tuple extension depending on endianness, defined to be respectively
'el' or 'eb' according to the endianness.

Some architecture do not use 'el' or 'eb', but use 'le' or 'be'.

Provide that as well, as two new variables: target_endian_le and
target_endian_be.

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Cody P Schafer <dev@codyps.com>
yann@2139
     1
reporter_name="Anthony Foiani <anthony.foiani@gmail.com>"
yann@2139
     2
reporter_url="http://sourceware.org/ml/crossgcc/2010-09/msg00100.html"
yann@2290
     3
reporter_comment="This is a sample config file for Freescale e500v2 processors (e.g., MPC8548,
yann@2369
     4
MPC8572). It uses eglibc (for e500/SPE patches) and a recent gcc (4.6.0,
yann@2173
     5
for e500v2 DPFP support) and will generate appropriate dual-precision
yann@2173
     6
floating point instructions by default.
yann@935
     7
yann@2173
     8
Note: If building a Linux kernel with this toolchain, you will want to make
yann@2173
     9
sure -mno-spe AND -mspe=no are passed to gcc to prevent SPE ABI/instructions
yann@2173
    10
from getting into the kernel (which is currently unsupported). At this time,
yann@2173
    11
the kernel build system properly passes those two options, but older kernels
yann@2173
    12
were only passing -mno-spe by default."