Skip to content
STIMSMITH

Compliance Assurance

Concept WIKI v1 · 7/6/2026

In the context of RISC-V hardware verification, Compliance Assurance refers to the technical activities and tools used to verify that processor cores and SoCs conform to the architectural specifications published by RISC-V International. It is one of the special verification requirements for the RISC-V ecosystem, alongside custom instruction verification and support for a broad range of architectures.

Compliance Assurance

Definition and Scope

Within the RISC-V verification ecosystem, Compliance Assurance is the engineering practice of verifying that processor cores and System-on-Chip (SoC) designs correctly implement the RISC-V Instruction Set Architecture (ISA) as defined by the governing body. It encompasses the automated test generation, coverage analysis, and certification activities that confirm a design conforms to the architectural compliance tests published for the architecture.

Role in the RISC-V Verification Stack

The open RISC-V ISA has been gaining significant traction across multiple application domains, but it presents verification challenges that differ from established commercial ISAs. Industry data referenced in RISC-V verification literature indicates that established vendors invest heavily in verification — on the order of $150M per year per core to reach approximately 10¹⁵ verification cycles. Reproducing that level of quality across the fragmented RISC-V ecosystem requires automation, reuse, and new verification methodologies.

Within this context, Compliance Assurance is listed as one of the special verification requirements specific to RISC-V, alongside:

  • Custom instruction verification — verifying vendor-specific extensions to the base ISA.
  • Compliance assurance — confirming conformance to architectural compliance tests.
  • Broad range of architectures — supporting diverse processor profiles from embedded cores to application processors.

Because different processors have different verification needs (embedded cores, processor clusters, application processors), compliance assurance must be combined with reuse and automation to meet quality expectations. Automated test generation is highlighted as a key technique enabling this.

Implementation and Governance

RISC-V International is developing a certification committee whose stated goal is to certify devices against architectural compliance tests. This organizational initiative provides the governance framework under which vendor compliance assurance activities are measured and recognized.

Broader Context

Although the term "Compliance Assurance" appears in many domains, in adjacent fields such as software privacy it refers to verifying that applications conform to legal frameworks (for example, GDPR) using techniques like static program analysis. The RISC-V-specific meaning above is the focus of this article.

See Also

LINKED ENTITIES

1 links
RISC-V International IMPLEMENTS

CITATIONS

4 sources
4 citations
[1] RISC-V International is developing a certification committee to certify devices against architectural compliance tests. RISC-V Core & SoC Verification (Breker Verification Systems, Verification Futures Reading 2024)
[2] Compliance assurance is one of the special verification requirements for RISC-V, alongside custom instruction verification and support for a broad range of architectures. RISC-V Core & SoC Verification (Breker Verification Systems, Verification Futures Reading 2024)
[3] Arm spends approximately $150M per year on 10^15 verification cycles per core, illustrating the scale challenge that RISC-V compliance assurance must address through automation and reuse. RISC-V Core & SoC Verification (Breker Verification Systems, Verification Futures Reading 2024)
[4] Different RISC-V processors (embedded cores, processor clusters, application processors) have different compliance assurance needs. RISC-V Core & SoC Verification (Breker Verification Systems, Verification Futures Reading 2024)