Re: [patch] move value_range_equiv class to own file

On Mon, 2020-05-18 at 20:08 +0200, Aldy Hernandez wrote: > We already moved the value_range class into its own class in the last > release. I think it's time to move the value_range_equiv stuff into its > own class, as it's a distraction from the VRP code. > > I've moved it to value-range-equiv

Re: [patch] move value_range_equiv class to own file

On Tue, 2020-05-19 at 09:09 +0200, Richard Biener wrote: > On Mon, May 18, 2020 at 8:13 PM Aldy Hernandez via Gcc-patches > wrote: > > We already moved the value_range class into its own class in the last > > release. I think it's time to move the value_range_equiv stuff into its > > own class, a

Re: [patch] move value_range_equiv class to own file

On Mon, May 18, 2020 at 8:13 PM Aldy Hernandez via Gcc-patches wrote: > > We already moved the value_range class into its own class in the last > release. I think it's time to move the value_range_equiv stuff into its > own class, as it's a distraction from the VRP code. > > I've moved it to valu

[patch] move value_range_equiv class to own file

We already moved the value_range class into its own class in the last release. I think it's time to move the value_range_equiv stuff into its own class, as it's a distraction from the VRP code. I've moved it to value-range-equiv.*, and gave it a semblance of order, by putting the constructors