Conversation
|
Note that this PR depends on the AreaExtract PR! |
| if row["COMP_SIM"].lower() == "true": | ||
| subprocess.run( | ||
| [ | ||
| "fud2", |
There was a problem hiding this comment.
To save this script some runtime, you can actually run Verilator without the profiler to obtain cycle counts! Like this:
fud2 <calyx_file> -o <out_file> --to dat --through verilator -s sim.data=<data_file>
The first entry in the json should be the cycle count :) I'd highly recommend doing this because the profiler is so slow...
(Note: the --through verilator is important since Cider doesn't produce cycle counts.)
29b65ae to
e0e814b
Compare
|
This pull request has not seen activity in 14 days and is being marked as stale. If you're continuing work on this, please reply and state how to get this PR in a mergeable state or what issues it is blocked on. If the PR is not ready for review, please mark it as a draft. The PR will be closed in 7 days if there is no further activity. |
|
This stale PR is being closed because it has not seen any activity in 7 days. If you're planning to continue work on it, please reopen it and mention how to make progress on it. |
Shamelessly copy-pasting from the readme:
Compare
Compare is a tool for comparing simulation and synthesis results for multiple
Calyx designs. It reads a CSV recipe, runs the corresponding
simulation and synthesis flows, and produces a summary table (CSV or visual).
Input
DESIGNexample.futil)COMP_SIM"True"to run simulationSIM_DATACOMP_SYNTH"True"to run synthesis and place & routeSYNTH_VARff)SYNTH_PERIOD7.00)Output
DESIGNSIM_CYCLESSYNTH_STATUSSYNTH_AREAEXEC_TIMESIM_CYCLES x SYNTH_PERIODInstallation and usage
$ uv tool install . $ compare -h (base) usage: compare [-h] [-v] [-p] [-o OUTPUT] inputThe default output is
stdout, but an output file can be specified with-o.The table can also be printed in "visual mode" with
-p. Verbose mode can beenabled with
-v.