The following fixes a long-standing VRP regression now that we can
safely use some equivalences during propagation.
Bootstrapped and tested on x86_64-unknown-linux-gnu, applied to trunk.
Richard.
2016-03-03 Richard Biener
PR tree-optimization/55936
* tree-vrp.c (compare_name
On Fri, 11 Jan 2013, Jakub Jelinek wrote:
> On Fri, Jan 11, 2013 at 12:06:04PM +0100, Richard Biener wrote:
> >
> > VRP no longer (since 4.1.2 at least) can optimize vrp06.c in one go
> > because we happen to chose a symbolic range when
>
> Just FYI, GCC never optimized that apparently, at least
On Fri, Jan 11, 2013 at 12:06:04PM +0100, Richard Biener wrote:
>
> VRP no longer (since 4.1.2 at least) can optimize vrp06.c in one go
> because we happen to chose a symbolic range when
Just FYI, GCC never optimized that apparently, at least in r10
(vrp06.c has been added in r100478) vrp did
VRP no longer (since 4.1.2 at least) can optimize vrp06.c in one go
because we happen to chose a symbolic range when
Intersecting
[j_12(D), j_12(D)] EQUIVALENCES: { i_9(D) j_12(D) i_24 i_26 } (4
elements)
and
[10, 30] EQUIVALENCES: { i_9(D) i_26 } (2 elements)
to
[j_12(D), j_12(D)] EQUI