https://bugs.kde.org/show_bug.cgi?id=468575
Bug ID: 468575
Summary: Add support for RISC-V
Classification: Developer tools
Product: valgrind
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: jsew...@acm.org
Reporter: petr.pa...@dagobah.cz
Target Milestone: ---
RISC-V [1, 2] is a modern open-standard architecture which has seen increasing
adoption lately.
I and a few other contributors have been working on adding support for this
architecture in Valgrind, using a downstream repository [3]. The port has
reached a state where I think it has a good quality to be added to the official
Valgrind project and continued to be developed there.
The port adds supports for the 64-bit RISC-V architecture, specifically for the
RV64GC instruction set which is what most Linux distributions currently target.
Support for further extensions is expected to be incrementally implemented in
the future, as more extensions get defined by architecture stewards and make it
into hardware.
The work is cut into 6 patches. The first three add new files specific only to
the port and they are split for Valgrind (Coregrind+tools), VEX and tests. The
last three modify already present files and are split in the same way.
Implementation mostly tries to stay consistent with arm64 and mips64. No new
Iops are currently added by the port but some new ones might be needed in the
future. For instance, support for the Zfh extension (half-precision
floating-point) will likely require a few additional Iops, although these
should be needed for the complete Armv8.2-A FP16 support too.
The port passes almost completely the Valgrind test suite. A few tests still
currently fail and need to be investigated.
The port gained some reasonable traction and a few other people contributed to
it in the last year by implementing missing bits and fixing various bugs.
[1] https://riscv.org/
[2] https://en.wikipedia.org/wiki/RISC-V
[3] https://github.com/petrpavlu/valgrind-riscv64
--
You are receiving this mail because:
You are watching all bug changes.
