Mercurialcrosstool-ng / file revision
summary | shortlog | changelog | graph | tags | branches | files | changeset | file | latest | revisions | annotate | diff | raw | help
patches/glibc/ports-2.13/220-section-comments.patch
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 http://sources.redhat.com/ml/binutils/2004-04/msg00665.html

     2 

     3 fixes building on some architectures (like m68k/arm/cris/etc...) because

     4 it does the right thing

     5 

     6 diff -durN glibc-2.13.orig/include/libc-symbols.h glibc-2.13/include/libc-symbols.h

     7 --- glibc-2.13.orig/include/libc-symbols.h	2009-03-14 00:51:46.000000000 +0100

     8 +++ glibc-2.13/include/libc-symbols.h	2009-11-13 00:50:07.000000000 +0100

     9 @@ -239,12 +239,12 @@

    10  #  define __make_section_unallocated(section_string)

    11  # endif

    12  

    13 -/* Tacking on "\n\t#" to the section name makes gcc put it's bogus

    14 +/* Tacking on "\n#APP\n\t#" to the section name makes gcc put it's bogus

    15     section attributes on what looks like a comment to the assembler.  */

    16  # ifdef HAVE_SECTION_QUOTES

    17 -#  define __sec_comment "\"\n\t#\""

    18 +#  define __sec_comment "\"\n#APP\n\t#\""

    19  # else

    20 -#  define __sec_comment "\n\t#"

    21 +#  define __sec_comment "\n#APP\n\t#"

    22  # endif

    23  # define link_warning(symbol, msg) \

    24    __make_section_unallocated (".gnu.warning." #symbol) \
crosstool-ng