Re: [PATCH] tree-optimization/98117 - fix range set by vectorization on niter IVs

2020-12-07 Thread Richard Biener
On Mon, 7 Dec 2020, Richard Sandiford wrote: > Richard Biener writes: > > This avoids the degenerate case of a TYPE_MAX_VALUE latch iteration > > count value causing wrong range info for the vector IV. There's > > still the case of VF == 1 where if we don't know whether we hit the > > above case

Re: [PATCH] tree-optimization/98117 - fix range set by vectorization on niter IVs

2020-12-07 Thread Richard Sandiford via Gcc-patches
Richard Biener writes: > This avoids the degenerate case of a TYPE_MAX_VALUE latch iteration > count value causing wrong range info for the vector IV. There's > still the case of VF == 1 where if we don't know whether we hit the > above case we cannot emit a range. > > Bootstrap and regtest runni

[PATCH] tree-optimization/98117 - fix range set by vectorization on niter IVs

2020-12-07 Thread Richard Biener
This avoids the degenerate case of a TYPE_MAX_VALUE latch iteration count value causing wrong range info for the vector IV. There's still the case of VF == 1 where if we don't know whether we hit the above case we cannot emit a range. Bootstrap and regtest running on x86_64-unknown-linux-gnu. 20