On Tue, Nov 05, 2019 at 08:07:53AM +0100, Richard Biener wrote:
> > I was using loop->simdlen to detect whether it was a SIMD loop and I don't
> > believe that was correct, as can be witnessed by the mass failures in
> > libgomp.
> > My apologies for not running this, didn't think of it!
> >
> > I found that these were failing because we do not handle vectorization of
> > epilogues correctly when SIMDUID is set. For now Jakub and I agreed to
> > disable
> > epilogue vectorization for loops where SIMDUID is set until we have fixed
> > this. See further comments inline.
> >
> > I bootstrapped it on aarch64 and x86_64, ran libgomp on both.
> >
> > This OK for trunk?
>
> OK. Can you remove the simdlen == 0 check as a followup?
Yeah, exactly, I wanted to ask what the point of the simdlen == 0 check is.
All a non-zero simdlen says is a user assertion that certain inter-loop
depencencies don't exist.
Jakub
