the wrong result of "vmerge_vvm_i32m1"

[Erucaaa]

the wrong result of "vmerge_vvm_i32m1"

[topperc]

I don't see anything obviously wrong. What compiler are you using?

[Erucaaa]

I don't see anything obviously wrong. What compiler are you using?

/opt/gcc10.2/native/lib/gcc/riscv64-linux-gnu/10.2.0/specs

but when I set a new variable array b to store the result, the print is true.....

int32_t b[16] = {0};
vse32_v_i32m1(b, v4, vl);
vse32_v_i32m1(b+4, v5, vl);
vse32_v_i32m1(b+8, v6, vl);

[topperc]

I didn't know that gcc 10.2 supported RISC-V vector intrinsics, but I'm most familiar with clang.

[zhongjuzhe]

It seems that you are using old and obsolete RVV intrinsic API.

For example, you should use __riscv_vse32_v_i32m1 instead of vse32_v_i32m1.

To get latest and stable RVV feature, you should use latest GCC (GCC-14).

It's simple, replace "gcc" directory in https://github.com/riscv-collab/riscv-gnu-toolchain with
https://github.com/gcc-mirror/gcc

Then build it. You will get latest RVV support.

[kito-cheng]

It seems a toolchain implementation bug and also it's not an upstream toolchain, so close.