On Thu, 11 Feb 2016, Christophe Lyon wrote:
> On 9 February 2016 at 13:42, Richard Biener wrote:
> >
> > It turns out if-conversions poor job on
> >
> > if (a)
> >x[i] = ...;
> > else
> >x[i] = ...;
> >
> > results in bogus uninit warnings of x[i] for a variety of reasons.
> > First of
On 9 February 2016 at 13:42, Richard Biener wrote:
>
> It turns out if-conversions poor job on
>
> if (a)
>x[i] = ...;
> else
>x[i] = ...;
>
> results in bogus uninit warnings of x[i] for a variety of reasons.
> First of all forwprop (aka match.pd simplification) doesn't fixup
> all of i
It turns out if-conversions poor job on
if (a)
x[i] = ...;
else
x[i] = ...;
results in bogus uninit warnings of x[i] for a variety of reasons.
First of all forwprop (aka match.pd simplification) doesn't fixup
all of if-conversions poor job as canonicalization sometimes
inverts the condit
