Overview
riscv-arch-tests is an Assembly-language, self-checking directed-test suite for the RISC-V Instruction Set Architecture. It is publicly available as the GitHub repository tenstorrent/riscv_arch_tests, which the public metadata describes as "Self checking RISC-V directed tests" (e8c8a109-6fbe-4965-932d-6dd8a9020ec5; https://github.com/tenstorrent/riscv_arch_tests).
Role in verification flows
In multi-level RISC-V processor verification methodologies, riscv-arch-tests is used together with riscv-tests as a standard compliance test suite executed inside an automated Continuous Integration pipeline. The compliance suites serve as "established benchmarks for verifying that the Instruction" set is implemented correctly, before the methodology proceeds to directed, benchmarking, and constrained-random test phases (e8c8a109-6fbe-4965-932d-6dd8a9020ec5).
What it validates
When integrated into a verification strategy, riscv-arch-tests is intended to provide exhaustive validation of ISA features, covering:
- Various opcodes,
- Extensions such as F, D, and C, and
- Proper interactions with system registers (CSRs)
This is reported as ensuring that "every aspect of the design is rigorously validated, from basic compliance to resilience under real-world conditions" (e8c8a109-6fbe-4965-932d-6dd8a9020ec5).
Relationship to directed testing
Because the suite consists of hand-written, self-checking tests that target specific architectural behavior, it implements the directed-testing technique. It is typically run first in a layered methodology, prior to real-world benchmarks and constrained-random generation tools such as RISCV-DV (e8c8a109-6fbe-4965-932d-6dd8a9020ec5).
Repository characteristics
Public metadata for the repository at the time of capture indicates:
- Primary language: Assembly,
- Stars: 124,
- Forks: 17,
- Last updated: 2026-06-11 (https://github.com/tenstorrent/riscv_arch_tests).
These figures are taken from the GitHub metadata accompanying the public context and are useful for orienting readers to the activity level of the project, but they are not claims about the technical content of the suite itself.