Binary-Compatible Executable

Concept

In the context of VP-RTL cross-level verification, a binary-compatible executable is a single compiled program that can be run unchanged on two different models of the same system — typically a Virtual Platform (VP) and a Register-Transfer Level (RTL) implementation — enabling trace comparison to detect behavioral mismatches between the models.

First seen 8/15/2026

Last seen 8/15/2026

Evidence 2 chunks

Wiki v1

WIKI

Binary-Compatible Executable

Definition

A binary-compatible executable is, within the scope of cross-level hardware verification, a single compiled program (instruction sequence) that runs without modification on two distinct models of the same target architecture: a Virtual Platform (VP) and an RTL implementation of that same architecture. Because the same binary executes on both models, the resulting traces can be compared directly to surface behavioral mismatches between the VP and the RTL [chunk:602e4b1c-1e15-4d0a-8fc1-211104e3503d].

READ FULL ARTICLE →

NEIGHBORHOOD

No graph connections found for this entity yet. It may appear in future ingestion runs.

explore full graph →

RELATIONSHIPS

1 connections

Cross-Level Verification ← uses 100% 2e

Cross-level verification uses binary-compatible executables that run on both VP and RTL models.

LINKED ENTITIES

1 links

Cross-Level Verification USES Extracted graph relationship

CITATIONS

4 sources

4 citations — click to collapse

[1] A binary-compatible executable allows the same compiled binary to run unchanged on both a Virtual Platform and an RTL model. Exploring the Parameter Space for Constrained Random Verification in Cross-Level Verification

[2] Binary-compatible executable models can serve as early system-level references for RTL verification, enabling software testing, functional verification, and platform/environment evaluation. Exploring the Parameter Space for Constrained Random Verification in Cross-Level Verification

[3] In the RISC-V cross-level setup, MicroRV32 (RTL SoC) and the corresponding RISC-V Virtual Platform are binary compatible, so the exact same executable runs on both models. Exploring the Parameter Space for Constrained Random Verification in Cross-Level Verification

[4] Varying instruction sequence length (e.g., 100, 1 000, and 10 000 instructions) produces executables of different lengths and affects both coverage behavior and bug-finding effectiveness in the cross-level setup. Exploring the Parameter Space for Constrained Random Verification in Cross-Level Verification