On Tue, 22 Sep 2015, Christophe Lyon wrote:
> On 23 July 2015 at 13:17, Richard Biener wrote:
> > On Thu, 23 Jul 2015, Kyrill Tkachov wrote:
> >
> >>
> >> On 23/07/15 10:02, Andreas Schwab wrote:
> >> > Richard Biener writes:
> >> >
> >> > > Index: gcc/testsuite/gcc.dg/torture/pr66952.c
> >> > >
On 23 July 2015 at 13:17, Richard Biener wrote:
> On Thu, 23 Jul 2015, Kyrill Tkachov wrote:
>
>>
>> On 23/07/15 10:02, Andreas Schwab wrote:
>> > Richard Biener writes:
>> >
>> > > Index: gcc/testsuite/gcc.dg/torture/pr66952.c
>> > > ==
On Thu, 23 Jul 2015, Kyrill Tkachov wrote:
>
> On 23/07/15 10:02, Andreas Schwab wrote:
> > Richard Biener writes:
> >
> > > Index: gcc/testsuite/gcc.dg/torture/pr66952.c
> > > ===
> > > --- gcc/testsuite/gcc.dg/torture/pr66952.c
On 23/07/15 10:02, Andreas Schwab wrote:
Richard Biener writes:
Index: gcc/testsuite/gcc.dg/torture/pr66952.c
===
--- gcc/testsuite/gcc.dg/torture/pr66952.c (revision 0)
+++ gcc/testsuite/gcc.dg/torture/pr66952.c (worki
Richard Biener writes:
> Index: gcc/testsuite/gcc.dg/torture/pr66952.c
> ===
> --- gcc/testsuite/gcc.dg/torture/pr66952.c(revision 0)
> +++ gcc/testsuite/gcc.dg/torture/pr66952.c(working copy)
> @@ -0,0 +1,28 @@
> +/* { dg-do
This PR shows an issue with ifcombine which ends up executing
stmts producing range info under a different condition than
before (always true). With a twisted enough maze we end up
miscompiling the testcase for this reason.
Thus the following patch which resets all flow-sensitive
info on defs in