Re: POWERPC64_TOC_POINTER_ALIGNMENT

2015-11-18 Thread Michael Meissner
ex abc8eaa..e3ec042 100644 > > --- a/gcc/config/rs6000/rs6000.c > > +++ b/gcc/config/rs6000/rs6000.c > > @@ -8059,12 +8059,17 @@ rs6000_cannot_force_const_mem (machine_mode mode > > ATTRIBUTE_UNUSED, rtx x) > > static bool > > use_toc_relative_ref (rtx sym, machin

Re: POWERPC64_TOC_POINTER_ALIGNMENT

2015-11-18 Thread David Edelsohn
059,17 @@ rs6000_cannot_force_const_mem (machine_mode mode > ATTRIBUTE_UNUSED, rtx x) > static bool > use_toc_relative_ref (rtx sym, machine_mode mode) > { > + /* Silence complaint that the POWERPC64_TOC_POINTER_ALIGNMENT test > + is always true. */ > +#pragma GCC dia

Re: POWERPC64_TOC_POINTER_ALIGNMENT

2015-11-17 Thread Alan Modra
ef (rtx sym, machine_mode mode) { + /* Silence complaint that the POWERPC64_TOC_POINTER_ALIGNMENT test + is always true. */ +#pragma GCC diagnostic push +#pragma GCC diagnostic ignored "-Wtype-limits" return ((constant_pool_expr_p (sym) && ASM_OUTPUT_SPECIAL_PO

Re: POWERPC64_TOC_POINTER_ALIGNMENT

2015-11-17 Thread Michael Meissner
On Wed, Nov 18, 2015 at 09:52:41AM +1030, Alan Modra wrote: > David noticed that gcc112 was generating gcc/auto-host.h with > #define POWERPC64_TOC_POINTER_ALIGNMENT 32768 > > This is not the correct value of either 8 or 256 depending on how old > ld is. On investigating I fou

POWERPC64_TOC_POINTER_ALIGNMENT

2015-11-17 Thread Alan Modra
David noticed that gcc112 was generating gcc/auto-host.h with #define POWERPC64_TOC_POINTER_ALIGNMENT 32768 This is not the correct value of either 8 or 256 depending on how old ld is. On investigating I found the cause is Fedora 21 modifying the toolchain to default to -z relro. ld -z relro