On 02/09/2018 05:14 PM, Segher Boessenkool wrote:
> Hi!
>
> On Fri, Feb 09, 2018 at 09:37:28AM +0000, 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... :-)
>
> So does it work? :-) (I cannot reproduce the problem, there must be
> something in your configuration I'm overlooking).
>
>
> Segher
>
>
> [ Here it is again, with changelog this time: ]
>
>
> From 44c3b661ef75e57415b10ca2cec5ac6427bbed8f Mon Sep 17 00:00:00 2001
> Message-Id:
> <44c3b661ef75e57415b10ca2cec5ac6427bbed8f.1518109128.git.seg...@kernel.crashing.org>
> From: Segher Boessenkool <seg...@kernel.crashing.org>
> Date: Thu, 8 Feb 2018 16:58:33 +0000
> Subject: [PATCH] Do not mess with rs6000_{single,double}_float (PR68028)
>
> For e500 family cores we do some questionable things with those flags,
> which does not work with LTO. So don't.
>
>
> 2018-02-10 Segher Boessenkool <seg...@kernel.crashing.org>
>
> * config/rs6000/rs6000.c (rs6000_option_override_internal): Don't
> handle rs6000_single_float and rs6000_double_float specially for
> e500 family CPUs.
That should work -- the whole issue here is the -mcpu=<whatever>
changing other flags. If your assertion is that we need not treat the
E500 family of cores special here, then let's just zap that code.
Jeff
