diff options
| author | Ignacio Encinas <ignacio@iencinas.com> | 2025-03-06 20:49:27 +0100 |
|---|---|---|
| committer | Alexandre Ghiti <alexghiti@rivosinc.com> | 2025-04-01 07:03:04 +0000 |
| commit | 79ba5c1c7767a539f42c6f6db46961b0bec2bc03 (patch) | |
| tree | 978ff76dc90bdd902900740bffa8edc421d5bd05 /rust/helpers/build_bug.c | |
| parent | 83d78ac677b9fdd8ea763507c6fe02d6bf415f3a (diff) | |
| download | linux-79ba5c1c7767a539f42c6f6db46961b0bec2bc03.tar.gz linux-79ba5c1c7767a539f42c6f6db46961b0bec2bc03.tar.bz2 linux-79ba5c1c7767a539f42c6f6db46961b0bec2bc03.zip | |
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
(-Wtautological-constant-out-of-range-compare) warn about this.
Reviewed-by: Charlie Jenkins <charlie@rivosinc.com>
Tested-by: Charlie Jenkins <charlie@rivosinc.com>
Signed-off-by: Ignacio Encinas <ignacio@iencinas.com>
Link: https://lore.kernel.org/r/20250306-fix-v_exec_initval_nolibc-v2-1-97f9dc8a7faf@iencinas.com
Signed-off-by: Alexandre Ghiti <alexghiti@rivosinc.com>
Diffstat (limited to 'rust/helpers/build_bug.c')
0 files changed, 0 insertions, 0 deletions