sv-analyzer

Block-level dataflow analysis engine for Verilog/SystemVerilog designs.

Quick Start

cargo build
cargo test --all-targets -v
cargo run -p sva_cli -- --help

Crates

Crate	Purpose
sva-core	Core library: AST, block, coverage, slicer, types, wave
sva-cli	CLI crate (sva_cli), exposed as dataflow-engine in help/output
sva-mcp	MCP server
sva-vscode	VSCode extension backend

CLI Usage

cargo run -p sva_cli -- blockize --sv <file> [--sv <file> ...]
cargo run -p sva_cli -- blockize --project-path <dir> [--include-paths <dir1,dir2,...>]

cargo run -p sva_cli -- blocks query --input <blockize-json> [--block-id <id>] [--output-signal <name> ...] [--input-signal <name> ...] [--scope <prefix>] [--block-type <kind>] [--circuit-type <kind>] [--source-file <suffix>]

cargo run -p sva_cli -- slice --static --sv <file> --signal <hierarchical-name>
cargo run -p sva_cli -- slice --static --project-path <dir> --signal <hierarchical-name> [--include-paths <dir1,dir2,...>]

cargo run -p sva_cli -- slice --sv <file> --vcd <file> [--tree-json <verilator-tree-json>] [--tree-meta-json <verilator-tree-meta-json>] --signal <hierarchical-name> --time <t> --min-time <t>
cargo run -p sva_cli -- coverage --sv <file> --vcd <file> --time <t>
cargo run -p sva_cli -- wave --vcd <file> --signal <hierarchical-name> --time <t>

Source Selection

• Use --sv to pass one or more explicit SystemVerilog source files.
• Use --project-path to scan a larger source tree recursively.
• --project-path currently discovers .sv files only. It skips .svh and other non-source files when walking a directory.
• --include-paths is a comma-separated list of extra include directories passed to sv_parser.
• At least one source must be provided through --sv or --project-path.

Notes

• Static and dynamic slice queries work best with hierarchical signal names in elaborated designs.
• If a signal name is ambiguous or missing, the CLI returns similar hierarchical names.
• The parser currently hardcodes the RVFI define for preprocessing.

Block Queries

• blocks query reads a saved blockize JSON file and returns full matching block JSON.
• All query properties are combined with logical AND.
• Repeated --output-signal and --input-signal flags require the block to contain every requested signal.
• --scope matches the exact module_scope or any hierarchical descendant.
• --source-file uses suffix matching, so rtl/ibex_if_stage.sv matches an absolute path ending in that suffix.

Example:

cargo run -p sva_cli -- blockize \
  --project-path /path/to/ibex/rtl \
  --sv /path/to/ibex/examples/simple_system/rtl/ibex_simple_system.sv \
  --include-paths /path/to/ibex/vendor/lowrisc_ip/ip/prim/rtl,/path/to/ibex/vendor/lowrisc_ip/dv/sv/dv_utils \
  > ibex_blocks.json

cargo run -p sva_cli -- blocks query \
  --input ibex_blocks.json \
  --scope TOP.ibex_simple_system.u_top.u_ibex_top.u_ibex_core.if_stage_i \
  --output-signal TOP.ibex_simple_system.u_top.u_ibex_top.u_ibex_core.if_stage_i.pc_id_o \
  --source-file rtl/ibex_if_stage.sv

Real Project Example

Ibex blockize with external include roots:

cargo run -p sva_cli -- blockize \
  --project-path /path/to/ibex/rtl \
  --include-paths /path/to/ibex/vendor/lowrisc_ip/ip/prim/rtl,/path/to/ibex/vendor/lowrisc_ip/dv/sv/dv_utils

Ibex static slice for the simple-system top-level:

cargo run -p sva_cli -- slice --static \
  --project-path /path/to/ibex/rtl \
  --sv /path/to/ibex/examples/simple_system/rtl/ibex_simple_system.sv \
  --include-paths /path/to/ibex/vendor/lowrisc_ip/ip/prim/rtl,/path/to/ibex/vendor/lowrisc_ip/dv/sv/dv_utils \
  --signal TOP.ibex_simple_system.u_top.u_ibex_top.u_ibex_core.if_stage_i.pc_id_o \
  > ibex_static_slice.json

Ibex dynamic (blues) slice for the simple-system top-level:

cargo run -p sva_cli -- slice \
  --project-path /path/to/ibex/rtl \
  --sv /path/to/ibex/examples/simple_system/rtl/ibex_simple_system.sv \
  --include-paths /path/to/ibex/vendor/lowrisc_ip/ip/prim/rtl,/path/to/ibex/vendor/lowrisc_ip/dv/sv/dv_utils \
  --vcd /path/to/ibex/build/lowrisc_ibex_ibex_simple_system_cosim_0/sim-verilator/sim.fst \
  --tree-json /path/to/ibex/build/lowrisc_ibex_ibex_simple_system_cosim_0/sim-verilator/Vibex_simple_system_027_begin.tree.json \
  --tree-meta-json /path/to/ibex/build/lowrisc_ibex_ibex_simple_system_cosim_0/sim-verilator/Vibex_simple_system.tree.meta.json \
  --signal TOP.ibex_simple_system.u_top.u_ibex_top.u_ibex_core.if_stage_i.pc_id_o \
  --clock TOP.ibex_simple_system.u_top.u_ibex_top.u_ibex_core.if_stage_i.clk_i \
  --clk-step 2 \
  --time 19 \
  --min-time 11 \
  > ibex_blues.json

The Ibex examples above use --project-path for ibex/rtl, and add examples/simple_system/rtl/ibex_simple_system.sv explicitly with --sv because that top-level wrapper is outside the scanned rtl/ tree.

For the native Verilator JSON setup and the observed pruning result, see ibex_native_verilator_blues_check.md.

Library Usage

use sva_core::ast::{AstProvider, SvParserProvider};
use sva_core::block::{Blockizer, DataflowBlockizer};
use sva_core::coverage::VcdCoverageTracker;
use sva_core::slicer::{BluesSlicer, SliceRequest, StaticSlicer};
use sva_core::types::{SignalNode, Timestamp};

let parsed = SvParserProvider.parse_files(&[...])?;
let blocks = DataflowBlockizer.blockize(&parsed)?;
let graph = StaticSlicer::new(blocks).slice(&SliceRequest { ... })?;

Architecture

Trait-based core: AstProvider, Blockizer, CoverageTracker, WaveformReader, Slicer.

Implementations: SvParserProvider, DataflowBlockizer, VcdCoverageTracker, WellenReader, StaticSlicer, BluesSlicer.

Dev Commands

cargo fmt --all
cargo clippy --all-targets --all-features -- -D warnings
cargo test --all-targets -v

Run cargo run -p sva_cli -- <subcommand> --help to inspect the current CLI surface.