[PATCH] devtools: add RISC-V vector in meson build test

[PATCH] devtools: add RISC-V vector in meson build test

[Sun Yuechi]

Signed-off-by: Sun Yuechi <sunyuechi@iscas.ac.cn>
---
 devtools/test-meson-builds.sh | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/devtools/test-meson-builds.sh b/devtools/test-meson-builds.sh
index 4fff1f7177..4f07f84eb0 100755
--- a/devtools/test-meson-builds.sh
+++ b/devtools/test-meson-builds.sh
@@ -290,6 +290,10 @@ build build-ppc64-power8-gcc $f ABI $use_shared
 f=$srcdir/config/riscv/riscv64_linux_gcc
 build build-riscv64-generic-gcc $f ABI $use_shared
 
+# RISC-V vector (rv64gcv)
+f=$srcdir/config/riscv/riscv64_rv64gcv_linux_gcc
+build build-riscv64_rv64gcv_gcc $f ABI $use_shared
+
 # Test installation of the x86-generic target, to be used for checking
 # the sample apps build using the pkg-config file for cflags and libs
 load_env cc
-- 
2.51.2

Re: [PATCH] devtools: add RISC-V vector in meson build test

[sunyuechi]

> Maybe we want to replace the generic RISC-V build with the vector one.
> It could be discussed in another patch.

I think both scalar and vector build detection should exist,
because I've seen several times in other projects that after adding vector optimization, 
the scalar version build failed due to incorrect compilation conditions. 
Some cautious projects also test various extension combinations. What do you think?


> -----原始邮件-----
&gt; 发件人: "Sun Yuechi" <sunyuechi@iscas.ac.cn>
&gt; 发送时间: 2025-11-10 10:52:20 (星期一)
&gt; 收件人: dev@dpdk.org
&gt; 抄送: "Sun Yuechi" <sunyuechi@iscas.ac.cn>, "Bruce Richardson" <bruce.richardson@intel.com>
&gt; 主题: [PATCH] devtools: add RISC-V vector in meson build test
&gt; 
&gt; Signed-off-by: Sun Yuechi <sunyuechi@iscas.ac.cn>
&gt; ---
&gt;  devtools/test-meson-builds.sh | 4 ++++
&gt;  1 file changed, 4 insertions(+)
&gt; 
&gt; diff --git a/devtools/test-meson-builds.sh b/devtools/test-meson-builds.sh
&gt; index 4fff1f7177..4f07f84eb0 100755
&gt; --- a/devtools/test-meson-builds.sh
&gt; +++ b/devtools/test-meson-builds.sh
&gt; @@ -290,6 +290,10 @@ build build-ppc64-power8-gcc $f ABI $use_shared
&gt;  f=$srcdir/config/riscv/riscv64_linux_gcc
&gt;  build build-riscv64-generic-gcc $f ABI $use_shared
&gt;  
&gt; +# RISC-V vector (rv64gcv)
&gt; +f=$srcdir/config/riscv/riscv64_rv64gcv_linux_gcc
&gt; +build build-riscv64_rv64gcv_gcc $f ABI $use_shared
&gt; +
&gt;  # Test installation of the x86-generic target, to be used for checking
&gt;  # the sample apps build using the pkg-config file for cflags and libs
&gt;  load_env cc
&gt; -- 
&gt; 2.51.2
</sunyuechi@iscas.ac.cn></bruce.richardson@intel.com></sunyuechi@iscas.ac.cn></sunyuechi@iscas.ac.cn>

Re: [PATCH] devtools: add RISC-V vector in meson build test

[Thomas Monjalon]

10/11/2025 03:54, sunyuechi@iscas.ac.cn:
> > Maybe we want to replace the generic RISC-V build with the vector one.
> > It could be discussed in another patch.
> 
> I think both scalar and vector build detection should exist,
> because I've seen several times in other projects that after adding vector optimization, 
> the scalar version build failed due to incorrect compilation conditions. 
> Some cautious projects also test various extension combinations. What do you think?

We can test it in a CI, but test-meson-builds.sh is supposed to be run
very frequently by all maintainers. I think it is too much.
As a comparison, in this script we test only
1 Arm target, 1 LoongArch, 1 Power.