> gcc/
>
> * tree-vect-loop-manip.cc (vect_do_peeling): Verify
> that vectorization factor is a compile-time constant.
>
> ---
> gcc/tree-vect-loop-manip.cc | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/gcc/tree-vect-loop-manip.cc b/gcc/tree-vect-loop-manip.cc
> index 6aa3d2ed0bf..1ad1961c788 100644
> --- a/gcc/tree-vect-loop-manip.cc
> +++ b/gcc/tree-vect-loop-manip.cc
> @@ -2930,7 +2930,7 @@ vect_do_peeling (loop_vec_info loop_vinfo, tree
> niters, tree nitersm1,
> niters = vect_build_loop_niters (loop_vinfo, &new_var_p);
> /* It's guaranteed that vector loop bound before vectorization is at
> least VF, so set range information for newly generated var. */
> - if (new_var_p)
> + if (new_var_p && vf.is_constant ())
> {
> value_range vr (type,
> wi::to_wide (build_int_cst (type, vf)),
I don't think we need to apply this limit in case of RVV auto-vectorization.
I have talked with Kito and I have a full solution of supporting RVV solution.
We are going to support RVV auto-vectorization in 3 configuration according to
RVV ISA spec:
1. -march=zve32* support QI and HI auto-vectorization by VNx4QImode and
VNx2HImode
2. -march=zve64* support QI and HI and SI auto-vectorization by VNx8QImode and
VNx4HImode and VNx2SImode
3. -march=v* support QI and HI and SI and DI auto-vectorization by VNx16QImode
and VNx8HImode and VNx4SImode and VNx2DImode
I will support them in GCC 14. Current loop vectorizer works well for us no
need to fix it.
Thanks.
juzhe.zh...@rivai.ai
