RE: [PATCH v2] RISC-V: Introduce gcc option mrvv-vector-bits for RVV

2024-02-28 Thread Li, Pan2
@gcc.gnu.org; juzhe.zh...@rivai.ai; Wang, Yanzhang ; rdapp@gmail.com; jeffreya...@gmail.com Subject: RE: [PATCH v2] RISC-V: Introduce gcc option mrvv-vector-bits for RVV Oh, I see, that indicates simply convert this option value to riscv_vector_chunks is not good enough here. I thought the term

RE: [PATCH v2] RISC-V: Introduce gcc option mrvv-vector-bits for RVV

2024-02-27 Thread Li, Pan2
...@rivai.ai; Wang, Yanzhang ; rdapp@gmail.com; jeffreya...@gmail.com Subject: Re: [PATCH v2] RISC-V: Introduce gcc option mrvv-vector-bits for RVV Keep SCALABLE, since it has different semantics with ZVL: -mrvv-vector-bits=scalble means zvl*b specify the minimal VLEN -mrvv-vector-bits=zvl means zvl*b

Re: [PATCH v2] RISC-V: Introduce gcc option mrvv-vector-bits for RVV

2024-02-27 Thread Kito Cheng
Keep SCALABLE, since it has different semantics with ZVL: -mrvv-vector-bits=scalble means zvl*b specify the minimal VLEN -mrvv-vector-bits=zvl means zvl*b specify the exactly VLEN What's difference exactly? -mrvv-vector-bits=scalble with zvl128b can run on any machine with VLEN >= 128