Re: [Valgrind-developers] valgrind riscv-linux port integrated

[Jeff L. <jef...@gm...>]

On 2/25/25 3:27 PM, Mark Wielaard wrote:
> 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.
That's fantastic news.

> 
> 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
Petr would be the most logical choice in my mind, but I can't speak for 
his willingness and time.


> 
> 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
Seems like either a test or toolchain problem.  GIven it's C code I'd 
lean towards the latter.

> 
> Also there seems to be an issue with larger programs with large stack
> frames which I haven't tracked down yet.
Definitely pass it along if it ultimately looks compiler related.  We do 
certainly support larger stack frames, though we have to jump through 
some hoops to make them work.  But I think once you get into the 
gigabyte ranges things might start to fall down.

jeff