Hi, On 2026-06-07 16:15, Adrian Bunk wrote: > Source: fftw3 > Version: 3.3.11-1 > Severity: serious > Tags: patch > Forwarded: https://github.com/FFTW/fftw3/pull/406 > X-Debbugs-Cc: [email protected] > User: [email protected] > Usertags: riscv64 > Control: affects -1 src:sndfile-tools > > https://ci.debian.net/packages/s/sndfile-tools/testing/riscv64/71828732/ > > ... > 177s autopkgtest [08:44:03]: test upstream-tests: [----------------------- > 184s valgrind /usr/bin/sndfile-generate-chirp : ok > 192s valgrind /usr/bin/sndfile-resample : 1 errors, 0 bytes leaked > 196s valgrind /usr/bin/sndfile-resample : 1 errors, 0 bytes leaked > 200s valgrind /usr/bin/sndfile-resample : 1 errors, 0 bytes leaked > 204s valgrind /usr/bin/sndfile-spectrogram : tests/test-wrapper.sh: line 15: > 1804 Illegal instruction $valgrind $@ > $logfile 2>&1 > 204s ok > 215s valgrind /usr/bin/sndfile-waveform : 0 errors, 432 bytes leaked > 215s autopkgtest [08:44:41]: test upstream-tests: -----------------------] > 215s autopkgtest [08:44:41]: test upstream-tests: - - - - - - - - - - > results - - - - - - - - - - > 215s upstream-tests FAIL stderr: tests/test-wrapper.sh: line 15: 1804 > Illegal instruction $valgrind $@ > $logfile 2>&1 > ... > > > A fix is attached.
Hmm, while the fix is correct for upstream, I do not think this is the correct fix for Debian. zicntr was part of the original rv64gc baseline when the port was created before it got split out. I think we should include it in our baseline, because anyway it is supported by all the boards we target and widely used in the binaries we ship. The real issue here is that valgrind doesn't support it (also not in the current upstream git), so probably that test should be disabled instead. Regards Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B [email protected] http://aurel32.net
