mirror of
https://github.com/YosysHQ/sby.git
synced 2025-10-24 18:04:36 +00:00
`SbyTask::update_status()` optionally takes the current step/depth, which gets used for some solvers/engines when exiting to pass unknown properties. btor engine tracks the current step, but it doesn't track/report which property triggered a CEX so it's only useful on exit. Use data source as a fallback if engine isn't provided (such as when coming from the `task_status` instead of an engine update). |
||
|---|---|---|
| .. | ||
| sby.py | ||
| sby_autotune.py | ||
| sby_cmdline.py | ||
| sby_core.py | ||
| sby_design.py | ||
| sby_engine_abc.py | ||
| sby_engine_aiger.py | ||
| sby_engine_btor.py | ||
| sby_engine_smtbmc.py | ||
| sby_jobserver.py | ||
| sby_mode_bmc.py | ||
| sby_mode_cover.py | ||
| sby_mode_live.py | ||
| sby_mode_prove.py | ||
| sby_sim.py | ||
| sby_status.py | ||