Re: [RS6000] CONST_DOUBLE tidy

2018-11-28 Thread Segher Boessenkool
On Thu, Nov 29, 2018 at 10:18:40AM +1030, Alan Modra wrote: > On Wed, Nov 28, 2018 at 12:14:55PM -0600, Segher Boessenkool wrote: > > On Sun, Nov 25, 2018 at 10:46:28PM +1030, Alan Modra wrote: > > > - /* If we are using V.4 style PIC, consider all constants to be hard. > > > */ > > > - if (fla

Re: [RS6000] CONST_DOUBLE tidy

2018-11-28 Thread Alan Modra
On Wed, Nov 28, 2018 at 12:14:55PM -0600, Segher Boessenkool wrote: > On Sun, Nov 25, 2018 at 10:46:28PM +1030, Alan Modra wrote: > > - /* If we are using V.4 style PIC, consider all constants to be hard. */ > > - if (flag_pic && DEFAULT_ABI == ABI_V4) > > -return 0; > > Did you remove this

Re: [RS6000] CONST_DOUBLE tidy

2018-11-28 Thread Segher Boessenkool
Hi! On Sun, Nov 25, 2018 at 10:46:28PM +1030, Alan Modra wrote: > Once upon a time CONST_DOUBLE was used to hold large integer constants > that didn't fit into a CONST_INT. Now that CONST_INT is always at > least 64 bits, and the rs6000 backend uses CONST_WIDE_INT for larger > integers, there is

[RS6000] CONST_DOUBLE tidy

2018-11-25 Thread Alan Modra
Once upon a time CONST_DOUBLE was used to hold large integer constants that didn't fit into a CONST_INT. Now that CONST_INT is always at least 64 bits, and the rs6000 backend uses CONST_WIDE_INT for larger integers, there is no need for old code dealing with integers in CONST_DOUBLE. The rs6000 b