On Wed, 6 Dec 2023, Tamar Christina wrote:
> > > Hi All,
> > >
> > > While waiting for reviews I found this case where both loop exit needs to
> > > go to
> > > epilogue loop, but there was an IV related variable that was used in the
> > > scalar
> > > iteration as well.
> > >
> > >
> -Original Message-
> From: Tamar Christina
> Sent: Wednesday, December 6, 2023 8:48 AM
> To: Richard Biener
> Cc: gcc-patches@gcc.gnu.org; nd ; j...@ventanamicro.com
> Subject: RE: [PATCH]middle-end: Fix peeled vect loop IV values.
>
> > > Hi All,
> &g
> > Hi All,
> >
> > While waiting for reviews I found this case where both loop exit needs to
> > go to
> > epilogue loop, but there was an IV related variable that was used in the
> > scalar
> > iteration as well.
> >
> > vect_update_ivs_after_vectorizer then blew the value away and replaced it
On Wed, 6 Dec 2023, Tamar Christina wrote:
> Hi All,
>
> While waiting for reviews I found this case where both loop exit needs to go
> to
> epilogue loop, but there was an IV related variable that was used in the
> scalar
> iteration as well.
>
> vect_update_ivs_after_vectorizer then blew
Hi All,
While waiting for reviews I found this case where both loop exit needs to go to
epilogue loop, but there was an IV related variable that was used in the scalar
iteration as well.
vect_update_ivs_after_vectorizer then blew the value away and replaced it with
the value if it took the
