[PATCH v2] selftests: riscv: fix v_exec_initval_nolibc.c

mits) and clang (-Wtautological-constant-out-of-range-compare) warn about this. Reviewed-by: Charlie Jenkins Tested-by: Charlie Jenkins Signed-off-by: Ignacio Encinas --- Changes in v2: Remove code that becomes useless now that the only "clean" value for vector registers is 0. - Link to v1:

[PATCH] selftests: riscv: fix v_exec_initval_nolibc.c

mits) and clang (-Wtautological-constant-out-of-range-compare) warn about this. Signed-off-by: Ignacio Encinas --- I tried looking why "all ones" was previously deemed a "clean" value but couldn't find any information. It looks like the kernel always zero-initializes the v

Re: [PATCH] selftests: riscv: fix v_exec_initval_nolibc.c

On 5/3/25 22:49, Charlie Jenkins wrote: > On Wed, Mar 05, 2025 at 05:39:28PM +0100, Ignacio Encinas wrote: >> Vector registers are zero initialized by the kernel. Stop accepting >> "all ones" as a clean value. >> >> Note that this was not working as expe