The part of a design a re-synthesis works on, and its way out to and back from ABC:
- extract the cut from the timing graph: the logic behind a set of end points, bounded by registers, ports and constants, with its primary inputs and outputs;
- write it to ABC, either as BLIF (with arrival and required times) or as a network mapped onto an ABC library built from the design's Liberty cells;
- put back what ABC returns: the old cells removed, the new ones and their nets created under unique names, every connection restored at the cut's boundary.
Part of Vyges Loom. A library, not a command:
vyges-rmplinks it forrestructureand theresynthfamily, and it ships inside thevyges-physicalbinary through it.
[dependencies]
vyges-cut = { git = "https://github.com/vyges-tools/cut", branch = "main" }The design and the timer are reached through two seams, so nothing here needs a database to be tested:
design::CutDesign(and the BLIF reader'sblif::BlifDesign) for the instances, nets and terminals it reads and edits;facts::Factsfor the timer's answers, one entry per graph vertex, gathered before the cut is built.
Instances, nets and vertices are visited in a fixed order (ids, then names), never in hash-map order, and new names come from a counter the caller owns, so the same design and the same ABC result give the same edited design on every run.
ABC is linked from the prebuilt archive of vyges-abc-lib:
export $(bash ../vyges-tools-abc-lib/scripts/fetch-bundle.sh "$PWD/.abc") # VYGES_ABC_PREBUILT_DIR
cargo test