recorded in the end.
Richard.
> Thanks.
>
>
> juzhe.zh...@rivai.ai
>
> From: Richard Biener
> Date: 2023-08-11 19:10
> To: juzhe.zh...@rivai.ai
> CC: gcc-patches; richard.sandiford; linkw; krebbel
> Subject: Re: Re: [PATCH V3] VECT: Support loop len control on EXT
>1, vectype, NULL);
> else
check here the target supports VEC_EXTRACT
> vect_record_loop_len (loop_vinfo,
> &LOOP_VINFO_LENS (loop_vinfo),
>
1, vectype, NULL);
> else
check here the target supports VEC_EXTRACT
> vect_record_loop_len (loop_vinfo,
> &LOOP_VINFO_LENS (loop_vinfo),
> 1, vectype,
loop_vinfo,
&LOOP_VINFO_LENS (loop_vinfo),
1, vectype, 1);
}
Thanks.
juzhe.zh...@rivai.ai
From: Richard Biener
Date: 2023-08-11 18:21
To: juzhe.zh...@rivai.ai
CC: gcc-patches; richard.sandiford; linkw; kr
On Fri, 11 Aug 2023, juzhe.zh...@rivai.ai wrote:
> Hi, Richi.
>
> >> So how can we resolve the issue when a non-VL operation like
> >> .VEC_EXTRACT is used for _len support?
>
> Do you mean non-VL extract last operation (I am sorry that not sure whether I
> understand your question correctly)?
Hi, Richi.
>> So how can we resolve the issue when a non-VL operation like
>> .VEC_EXTRACT is used for _len support?
Do you mean non-VL extract last operation (I am sorry that not sure whether I
understand your question correctly)?
If yes, the answer is for RVV, we are reusing the same flow as
