Mercurialcrosstool-ng / file revision
summary | shortlog | changelog | graph | tags | branches | files | changeset | file | latest | revisions | annotate | diff | raw | help
config/arch/microblaze.in
author "Yann E. MORIN" <yann.morin.1998@free.fr>
Sun Nov 25 18:22:38 2012 +0100 (2012-11-25)
changeset 3133 36aa2ae92c29
permissions -rw-r--r--
cc/gcc: do not print 'core' or 'final'

In gcc-'s core and final passes, do not print 'core' or 'final' in
log messages. We already print it in step messages.

Also, as we use the core backend to build the bare-metal final gcc,
it can be disturbing to read 'core' while we're in fact in 'final'.

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> 
     1 # MicroBlaze specific config options

     2 

     3 ## depends on EXPERIMENTAL

     4 ##

     5 ## select ARCH_SUPPORT_ARCH

     6 ## select ARCH_FLOAT_SW

     7 ## select ARCH_SUPPORTS_BOTH_ENDIAN

     8 ## select ARCH_DEFAULT_BE

     9 ## select ARCH_SUPPORTS_BOTH_MMU

    10 ## select ARCH_DEFAULT_HAS_MMU

    11 ##

    12 ## help The MicroBlaze architecture, as defined by:

    13 ## help 	http://www.xilinx.com/

    14 ## help 

    15 ## help Upstream projects do not currently provide

    16 ## help full support for the microblaze architecture

    17 ## help and as such, this is marked as EXPERIMENTAL

    18 ## help for CT-NG.

    19 ## help 

    20 ## help Support is being added for a modern gcc,

    21 ## help binutils and gdb along with nptl threading

    22 ## help in eglibc for microblaze.
crosstool-ng