Re: POWERPC64_TOC_POINTER_ALIGNMENT

2015-11-18 Thread Michael Meissner
On Wed, Nov 18, 2015 at 10:35:36AM -0500, David Edelsohn wrote: > On Tue, Nov 17, 2015 at 9:32 PM, Alan Modra wrote: > > On Tue, Nov 17, 2015 at 07:53:18PM -0500, Michael Meissner wrote: > >> Here is the temporary patch I'm using to get past rs6000.c. But I suspect > >> the > >> TOC alignment sh

Re: POWERPC64_TOC_POINTER_ALIGNMENT

2015-11-18 Thread David Edelsohn
On Tue, Nov 17, 2015 at 9:32 PM, Alan Modra wrote: > On Tue, Nov 17, 2015 at 07:53:18PM -0500, Michael Meissner wrote: >> Here is the temporary patch I'm using to get past rs6000.c. But I suspect >> the >> TOC alignment should never be 256. > > Yes, it should be. Recent GNU ld aligns .TOC. to a

Re: POWERPC64_TOC_POINTER_ALIGNMENT

2015-11-17 Thread Alan Modra
On Tue, Nov 17, 2015 at 07:53:18PM -0500, Michael Meissner wrote: > Here is the temporary patch I'm using to get past rs6000.c. But I suspect the > TOC alignment should never be 256. Yes, it should be. Recent GNU ld aligns .TOC. to a 256 byte boundary. I have this patch in my tree. diff --git a

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 found the cause is Fedo