[Valgrind-developers] valgrind riscv-linux port integrated

[Mark W. <ma...@kl...>]

Hi all,

The riscv-linux port started by Petr Pavlu and discussed in
https://bugs.kde.org/show_bug.cgi?id=468575
has finally been integrated into the main valgrind sources.

We don't have a valgrind riscv arch maintainer yet (any volunteers?)
but there are two buildbot builders:
https://builder.sourceware.org/buildbot/#/builders/valgrind-fedora-riscv
https://builder.sourceware.org/buildbot/#/builders/valgrind-ubuntu-riscv

The fedora builder runs on the starfive workers with Fedora release 40
(Forty) Linux 6.1.15-legacy-k1 GNU C Library (GNU libc) stable release
version 2.39. gcc 14.1.1 binutils 2.42

The unbuntu builder runs on the bpi-f3 workers with Ubuntu 24.04.1
LTS Linux 6.8.0-52-generic Ubuntu GLIBC 2.39-0ubuntu8.3. gcc 14.2.0
GNU Binutils 2.43.1

The regtest results on the fedora setup look really good:
== 748 tests, 1 stderr failure, 0 stdout failures, 0 stderrB failures, 1 stdoutB failure, 0 post failures ==
gdbserver_tests/hgtls                    (stdoutB)
drd/tests/pth_mutex_signal               (stderr)

Unfortunately the ubuntu setup cannot build two of the new tests:

compressed.o: in function `test_compressed_10':
/var/lib/buildbot/workers/sourceware/valgrind-ubuntu-riscv/build/none/tests/riscv64/compressed.c:347:(.text+0x56d26): dangerous relocation: The addend isn't allowed for R_RISCV_GOT_HI20

integer.o: in function `test_integer_shared':
/var/lib/buildbot/workers/sourceware/valgrind-ubuntu-riscv/build/none/tests/riscv64/integer.c:81:(.text+0x22cdc): dangerous relocation: The addend isn't allowed for R_RISCV_GOT_HI20

Also there seems to be an issue with larger programs with large stack
frames which I haven't tracked down yet.

Testing and fixes highly appreciated.

Cheers,

Mark