PATCH, spu: quieten libgcc builds

Trevor_Smigiel@playstation.sony.com Trevor_Smigiel@playstation.sony.com
Thu Dec 4 03:57:00 GMT 2008


Ben,

Could you provide details on which libgcc functions are causing the
messages?  And why it is ok to ignore them?

Can we disable the warning on just the files that cause them?

My concern is that we end up hiding real errors.

Trevor


* Ben Elliston <bje@au1.ibm.com> [2008-12-03 19:45]:
> This patch passes -mno-error-reloc to compiler on spu-elf when building
> libgcc to silence warnings about runtime relocations.  Would the status
> quo make more sense on spu targets other than spu-elf?  For this
> configuration, though, perhaps it's best to just silence these warnings?
> 
> Cheers, Ben
> 
> 2008-12-04  Ben Elliston  <bje@au.ibm.com>
> 
>         * config/spu/t-spu-elf (TARGET_LIBGCC2_CFLAGS): Pass
>         -mno-error-reloc instead of -mwarn-reloc to eliminate both
>         warnings and errors about runtime relocations.
> 
> Index: t-spu-elf
> ===================================================================
> --- t-spu-elf   (revision 142417)
> +++ t-spu-elf   (working copy)
> @@ -22,7 +22,7 @@ NATIVE_SYSTEM_HEADER_DIR = /include
>  LIBGCC1 =
>  CROSS_LIBGCC1 =
>  
> -TARGET_LIBGCC2_CFLAGS = -fPIC -mwarn-reloc -D__IN_LIBGCC2
> +TARGET_LIBGCC2_CFLAGS = -fPIC -mno-error-reloc -D__IN_LIBGCC2
>  
>  # We exclude those because the libgcc2.c default versions do not support
>  # the SPU single-precision format (round towards zero).  We provide our
> 



More information about the Gcc-patches mailing list