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

On Thu, Mar 06, 2025 at 07:31:22AM +0100, Ignacio Encinas Rubio wrote: > > > 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. > >>

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 expected given that >> value == 0xff >> c

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

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 expected given that > value == 0xff > can be assumed to be always false by the compiler

[PATCH] selftests: riscv: fix v_exec_initval_nolibc.c

Vector registers are zero initialized by the kernel. Stop accepting "all ones" as a clean value. Note that this was not working as expected given that value == 0xff can be assumed to be always false by the compiler as value's range is [-128, 127]. Both GCC (-Wtype-limits) and clang (-Wtaut