9 entities and 13 documented connections shown.
Drag the map or use pan buttons to move. Tab to a node or connection and press Enter to inspect its evidence. Arrows follow the actual claim direction.
| Subject | Relationship | Object | Status | Evidence |
|---|---|---|---|---|
| cocotb | Verilator | SUPPORTEDValidity dates not established | Why are these connected?Verilator documentation names cocotb as a library that supports Verilator. This establishes cocotb as the support provider; versions and execution are not established by this source. verilator pinned upstream documentationVerilator documentation names cocotb as a library that supports Verilator. This establishes cocotb as the support provider; versions and execution are not established by this source.
| |
| SymbiYosys | Yosys | SUPPORTEDValidity dates not established | Why are these connected?SymbiYosys describes itself as a front-end for Yosys-based formal verification flows; solver and frontend selection affect applicability. symbiyosys pinned upstream documentationSymbiYosys describes itself as a front-end for Yosys-based formal verification flows; solver and frontend selection affect applicability.
| |
| OpenLane 2 | Yosys | SUPPORTEDValidity dates not established | Why are these connected?OpenLane describes Yosys among its infrastructure components. openlane2 pinned upstream documentationOpenLane describes Yosys among its infrastructure components.
| |
| Yosys | SymbiYosys | SUPPORTEDValidity dates not established | Why are these connected?The Yosys README links SBY as its formal verification front-end; installed solvers and supported syntax remain separate requirements. yosys pinned upstream documentationThe Yosys README links SBY as its formal verification front-end; installed solvers and supported syntax remain separate requirements.
| |
| OpenROAD Flow Scripts | Yosys | SUPPORTEDValidity dates not established | Why are these connected?The OpenROAD README describes an ORFS flow whose synthesis stage uses Yosys. The OpenROAD application itself is not the complete ORFS flow. openroad pinned upstream documentationThe OpenROAD README describes an ORFS flow whose synthesis stage uses Yosys. The OpenROAD application itself is not the complete ORFS flow.
| |
| Yosys | Verilator | SUPPORTEDValidity dates not established | Why are these connected?The README recommends a separate Verilator lint check because the read_verilog command does not perform syntax checking. yosys pinned upstream documentationThe README recommends a separate Verilator lint check because the read_verilog command does not perform syntax checking.
| |
| Ibex | Yosys | SUPPORTEDValidity dates not established | Why are these connected?Ibex README describes Yosys area evaluation using its basic synthesis flow and latch-based register file. No area figures are republished. ibex pinned upstream documentationIbex README describes Yosys area evaluation using its basic synthesis flow and latch-based register file. No area figures are republished.
| |
| OSS CAD Suite | Verilator | SUPPORTEDValidity dates not established | Why are these connected?Listed distribution component at the pinned README revision; availability depends on the upstream release and supported platform. Component license is not replaced by the distribution license. OSS CAD Suite READMEThe OSS CAD Suite README lists Verilator among its distribution components.
| |
| Ibex | Verilator | SUPPORTEDValidity dates not established | Why are these connected?Ibex Simple System simulation example requires Verilator; this is a specific example, not a guarantee for every Ibex configuration. ibex pinned upstream documentationIbex Simple System simulation example requires Verilator; this is a specific example, not a guarantee for every Ibex configuration.
| |
| OSS CAD Suite | Yosys | SUPPORTEDValidity dates not established | Why are these connected?Listed distribution component at the pinned README revision; availability depends on the upstream release and supported platform. Component license is not replaced by the distribution license. OSS CAD Suite READMEThe OSS CAD Suite README lists Yosys among its distribution components.
| |
| cocotb | Verilator | SUPPORTEDValidity dates not established | Why are these connected?This cocotb source revision documents Verilator 5.036 or newer and SIM=verilator. This is upstream support with documented simulator-specific limitations. cocotb pinned upstream documentationThis cocotb source revision documents Verilator 5.036 or newer and SIM=verilator. This is upstream support with documented simulator-specific limitations.
| |
| Ibex | FuseSoC | SUPPORTEDValidity dates not established | Why are these connected?The Simple System simulator build described here is driven by FuseSoC. ibex pinned upstream documentationThe Simple System simulator build described here is driven by FuseSoC.
| |
| OpenROAD Flow Scripts | Yosys | SUPPORTEDValidity dates not established | Why are these connected?Yosys is documented for the synthesis stage of OpenROAD Flow Scripts at this source revision. OpenROAD Flow Scripts READMEThe ORFS flow diagram assigns logic synthesis to Yosys.
|
From Ibex · up to two relationship steps.
A path retains its original claims. Shared technology does not establish a supply contract.
Relationships may describe different dates. A path does not establish simultaneous activity. Bounded source-backed collection. Missing or filtered connections do not establish absence. Supported does not mean independently verified.
VLSI Korea