Use of uninitialized value test parameters
In some configurations, I got valgrind errors related to uninintialized value in getrf_nopiv tests.
Steps to reproduce :
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 22.04.3 LTS
Release: 22.04
Codename: jamm
$ clang --version
Ubuntu clang version 14.0.0-1ubuntu1.1
Target: x86_64-pc-linux-gnu
Thread model: posix
InstalledDir: /usr/bin
$ cmake -Bbuild
-DCMAKE_C_COMPILER=clang
-DCMAKE_BUILD_TYPE=Debug
-DCMAKE_C_FLAGS_DEBUG=-gdwarf-4
-DCMAKE_PREFIX_PATH=$HOME/.local
-DCMAKE_INCLUDE_PATH=$HOME/.local/include
-DCMAKE_LIBRARY_PATH=$HOME/.local/lib
$ cmake --build build
$ cd build/testing
$ valgrind ./chameleon_ztesting "-c" "-t" "2" "-g" "0" "-P" "1" "-f" "input/getrf_nopiv.in"
# ...
==290340== Conditional jump or move depends on uninitialised value(s)
==290340== at 0xBE9BCB8: __printf_fp_l (printf_fp.c:396)
==290340== by 0xBEB792C: __printf_fp_spec (vfprintf-internal.c:354)
==290340== by 0xBEB792C: __vfprintf_internal (vfprintf-internal.c:1558)
==290340== by 0xBEC2988: __vsprintf_internal (iovsprintf.c:95)
==290340== by 0xBEA1927: sprintf (sprintf.c:30)
==290340== by 0x1450B8: sprint_complex64 (testing/values.c:489)
==290340== by 0x146D02: run_print_line_partial (testing/run_list.c:948)
==290340== by 0x146E17: run_print_line (testing/run_list.c:1005)
==290340== by 0x11941C: main (chameleon_ztesting.c:249)
# ...
Adding the missing variable "bump" for the test "getrf_nopiv", the valgrind errors disappear :
$ echo "bump = 16" >> input/getrf_nopiv.in
$ valgrind ./chameleon_ztesting "-c" "-t" "2" "-g" "0" "-P" "1" "-f" "input/getrf_nopiv.in"
# no valgrind error appearing here
I could not reproduce it with gcc.
May be related to an issue with test variable initialization and default values #107.