> > > + && LOOP_VINFO_LOOP_IV_COND (loop_vinfo) != cond)
> > > + *relevant = vect_used_in_scope;
>
> but why not simply mark all gconds as vect_used_in_scope?
>
We break outer-loop vectorization since doing so would pull the inner loop's
exit into scope for the outerloop. Also we can't force
On Wed, 6 Dec 2023, Tamar Christina wrote:
> > > > + && LOOP_VINFO_LOOP_IV_COND (loop_vinfo) != cond)
> > > > + *relevant = vect_used_in_scope;
> >
> > but why not simply mark all gconds as vect_used_in_scope?
> >
>
> We break outer-loop vectorization since doing so would pull the
Ping
> -Original Message-
> From: Tamar Christina
> Sent: Monday, November 6, 2023 7:40 AM
> To: gcc-patches@gcc.gnu.org
> Cc: nd ; rguent...@suse.de; j...@ventanamicro.com
> Subject: [PATCH 10/21]middle-end: implement relevancy analysis support for
> control flow
>
> Hi All,
>
> This u
On Mon, 27 Nov 2023, Tamar Christina wrote:
> Ping
>
> > -Original Message-
> > From: Tamar Christina
> > Sent: Monday, November 6, 2023 7:40 AM
> > To: gcc-patches@gcc.gnu.org
> > Cc: nd ; rguent...@suse.de; j...@ventanamicro.com
> > Subject: [PATCH 10/21]middle-end: implement relevancy
