aboutsummaryrefslogtreecommitdiffstats
path: root/passes/cmds/bugpoint.cc
Commit message (Collapse)AuthorAgeFilesLines
* bugpoint: add -assigns and -updates options.whitequark2019-07-091-9/+81
|
* bugpoint: check for -script option.whitequark2019-05-141-0/+3
| | | | Fixes #925.
* Fix all warnings that occurred when compiling with gcc9Kristoffer Ellersgaard Koch2019-05-081-2/+1
|
* Add "whitebox" attribute, add "read_verilog -wb"Clifford Wolf2019-04-181-4/+4
| | | | Signed-off-by: Clifford Wolf <clifford@clifford.at>
* Switch "bugpoint" from system() to run_command()Clifford Wolf2019-01-071-1/+1
| | | | Signed-off-by: Clifford Wolf <clifford@clifford.at>
* bugpoint: new pass.whitequark2019-01-071-0/+369
A typical use of `bugpoint` would involve a script with a pass under test, e.g.: flowmap -relax -optarea 100 and would be invoked as: bugpoint -yosys ./yosys -script flowmap.ys -clean -cells This replaces the current design with the minimal design that still crashes the `flowmap.ys` script. `bugpoint` can also be used to perform generic design minimization using `select`, e.g. the following script: select i:* %x t:$_MUX_ %i -assert-max 0 would remove all parts of the design except for an unbroken path from an input to an output port that goes through exactly one $_MUX_ cell. (The condition is inverted.)