Skip to main content
VLSI Korea

Semiconductor graph

OpenROAD Flow Scripts
Methods ↗

5 entities and 4 documented connections shown.

Connections

5 entities · 4 claims
100%

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.

STARTING ENTITYDIRECT CONNECTIONSSECOND STEPUses tool · SUPPORTEDUses toolUses tool · SUPPORTEDUses toolIncludes · SUPPORTEDIncludesUses tool · SUPPORTEDUses toolYosys · eda toolEDA TOOLYosysKLayout · eda toolEDA TOOLKLayoutOSS CAD Suite · open source projectOPEN SOURCE PROJECTOSS CAD SuiteOpenROAD · eda toolEDA TOOLOpenROADOpenROAD Flow Scripts · open source projectOPEN SOURCE PROJECTSTARTOpenROAD FlowScripts
CompanyChip / productTechnologyPlace / facility
Select a connection for its evidence
Relationships & evidence (4)
Every displayed connection is a scoped claim. Arrows follow subject to object.
SubjectRelationshipObjectStatusEvidence
OpenROAD Flow ScriptsKLayoutSUPPORTEDValidity dates not established
Why are these connected?

KLayout is documented for the finishing stage. This is not a verified signoff result.

OpenROAD Flow Scripts README

The OpenROAD Project · Tier A · Primary source · supports

The ORFS flow diagram assigns GDSII generation and DRC/LVS checks to KLayout.

Location: Pinned README.md line 43: GDSII generation and layout checks

Published
Not stated
Retrieved
2026-10-13

Store factual paraphrases, metadata, source-byte SHA-256 and pinned document link only. Source bytes were fetched for this review but are not retained or redistributed. Repository and component licenses remain separate. Commit date is not document publication or relationship validity.

Full claim history →
OpenROAD Flow ScriptsOpenROADSUPPORTEDValidity dates not established
Why are these connected?

ORFS documents OpenROAD use. Its README restricts guarantees to the latest matching OpenROAD/ORFS and warns that third-party versions are not guaranteed.

OpenROAD Flow Scripts README

The OpenROAD Project · Tier A · Primary source · supports

The ORFS installation documentation identifies OpenROAD among its provided flow applications.

Location: Pinned README.md line 89: Physical implementation flow

Published
Not stated
Retrieved
2026-10-13

Store factual paraphrases, metadata, source-byte SHA-256 and pinned document link only. Source bytes were fetched for this review but are not retained or redistributed. Repository and component licenses remain separate. Commit date is not document publication or relationship validity.

Full claim history →
OSS CAD SuiteYosysSUPPORTEDValidity 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 README

YosysHQ · Tier A · Primary source · supports

The OSS CAD Suite README lists Yosys among its distribution components.

Location: Pinned README.md line 33: RTL synthesis

Published
Not stated
Retrieved
2026-10-13

Store factual paraphrases, metadata, source-byte SHA-256 and pinned document link only. Source bytes were fetched for this review but are not retained or redistributed. Repository and component licenses remain separate. Commit date is not document publication or relationship validity.

Full claim history →
OpenROAD Flow ScriptsYosysSUPPORTEDValidity 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 README

The OpenROAD Project · Tier A · Primary source · supports

The ORFS flow diagram assigns logic synthesis to Yosys.

Location: Pinned README.md line 19: RTL synthesis

Published
Not stated
Retrieved
2026-10-13

Store factual paraphrases, metadata, source-byte SHA-256 and pinned document link only. Source bytes were fetched for this review but are not retained or redistributed. Repository and component licenses remain separate. Commit date is not document publication or relationship validity.

Full claim history →
Find an evidence path

Find a documented path

From OpenROAD Flow Scripts · up to two relationship steps.

A path retains its original claims. Shared technology does not establish a supply contract.

5 nodes · 4 claims
Scope

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.