Re: RFA: Fix PR 68028: LTO error when compiling PowerPC binaries with single precision floating point

On Fri, Feb 16, 2018 at 06:05:13PM -0700, Jeff Law wrote: > > From: Segher Boessenkool > > Date: Thu, 8 Feb 2018 16:58:33 + > > Subject: [PATCH] Do not mess with rs6000_{single,double}_float (PR68028) > > > > For e500 family cores we do some questionable things

Re: RFA: Fix PR 68028: LTO error when compiling PowerPC binaries with single precision floating point

On 02/09/2018 05:14 PM, Segher Boessenkool wrote: > Hi! > > On Fri, Feb 09, 2018 at 09:37:28AM +, Nick Clifton wrote: >>> I thought you were going to do a patch like the following, to make the >>> e500 cores less special (they are not): >> >> Sorry - my bad. I defer to your patch then.

Re: RFA: Fix PR 68028: LTO error when compiling PowerPC binaries with single precision floating point

Hi! On Fri, Feb 09, 2018 at 09:37:28AM +, Nick Clifton wrote: > > I thought you were going to do a patch like the following, to make the > > e500 cores less special (they are not): > > Sorry - my bad. I defer to your patch then. Whatever it takes to get > the BZ fixed and off the books...

Re: RFA: Fix PR 68028: LTO error when compiling PowerPC binaries with single precision floating point

Hi Segher, > I thought you were going to do a patch like the following, to make the > e500 cores less special (they are not): Sorry - my bad. I defer to your patch then. Whatever it takes to get the BZ fixed and off the books... :-) Cheers Nick

Re: RFA: Fix PR 68028: LTO error when compiling PowerPC binaries with single precision floating point

Hi Nick, On Thu, Feb 08, 2018 at 03:49:38PM +, Nick Clifton wrote: > I should note that Richard Guenther feels that there is a better way > to solve the problem - by only initializing the values once - but I > still like my solution, so I am offering it here. I thought you were going

RFA: Fix PR 68028: LTO error when compiling PowerPC binaries with single precision floating point

Hi Segher, OK, here is an official submission of my patch to fix PR 68028. I should note that Richard Guenther feels that there is a better way to solve the problem - by only initializing the values once - but I still like my solution, so I am offering it here. OK to apply ? Cheers