Re: [patch] new API for value_range

2018-10-21 Thread Aldy Hernandez
Is this fixed by Richard's patch to 87640? if so, perhaps this is a duplicate of said PR. On Sun, Oct 21, 2018 at 3:34 AM H.J. Lu wrote: > > On Wed, Oct 17, 2018 at 7:39 AM Aldy Hernandez wrote: > > > > > > > > On 10/17/18 6:50 AM, Richard Biener wrote: > > > On Thu, Oct 11, 2018 at 8:25 PM Aldy

Re: [patch] new API for value_range

2018-10-20 Thread H.J. Lu
On Wed, Oct 17, 2018 at 7:39 AM Aldy Hernandez wrote: > > > > On 10/17/18 6:50 AM, Richard Biener wrote: > > On Thu, Oct 11, 2018 at 8:25 PM Aldy Hernandez wrote: > >> > >> > >> > >> On 10/11/18 5:47 AM, Richard Biener wrote: > >>> On Thu, Oct 11, 2018 at 10:19 AM Aldy Hernandez wrote: > >

Re: [patch] new API for value_range

2018-10-17 Thread Aldy Hernandez
On 10/17/18 6:50 AM, Richard Biener wrote: On Thu, Oct 11, 2018 at 8:25 PM Aldy Hernandez wrote: On 10/11/18 5:47 AM, Richard Biener wrote: On Thu, Oct 11, 2018 at 10:19 AM Aldy Hernandez wrote: Hi Richard. Thanks for reviewing. On 10/10/18 6:27 AM, Richard Biener wrote: On Tue, Oc

Re: [patch] new API for value_range

2018-10-17 Thread Richard Biener
On Thu, Oct 11, 2018 at 8:25 PM Aldy Hernandez wrote: > > > > On 10/11/18 5:47 AM, Richard Biener wrote: > > On Thu, Oct 11, 2018 at 10:19 AM Aldy Hernandez wrote: > >> > >> Hi Richard. Thanks for reviewing. > >> > >> On 10/10/18 6:27 AM, Richard Biener wrote: > >>> On Tue, Oct 9, 2018 at 6:23 P

Re: [patch] new API for value_range

2018-10-11 Thread Richard Biener
On Thu, Oct 11, 2018 at 10:19 AM Aldy Hernandez wrote: > > Hi Richard. Thanks for reviewing. > > On 10/10/18 6:27 AM, Richard Biener wrote: > > On Tue, Oct 9, 2018 at 6:23 PM Aldy Hernandez wrote: > >> > >> I'm assuming the silence on the RFC means nobody is viscerally opposed > >> to it, so her

Re: [patch] new API for value_range

2018-10-10 Thread Richard Biener
On Tue, Oct 9, 2018 at 6:23 PM Aldy Hernandez wrote: > > I'm assuming the silence on the RFC means nobody is viscerally opposed > to it, so here goes the actual implementation ;-). > > FWI: https://gcc.gnu.org/ml/gcc-patches/2018-10/msg00157.html > > My aim is no change to the current func