You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now the script infrastructure for regtests, running suites of designs etc. in vtr assumes each benchmark consists of one file. We're slightly weakening that by allowing .vh include files, but it would be good to allow benchmarks to include an arbitrary list of files as that is usually how they are created. Right now we have to concatenate all the hdl into one big file, purely for script convenience.
Proposed Behaviour
Allow run_vtr_task, run_vtr_flow and config.txt to all take an argument of either:
a single benchmark hdl file (e.g. ch_intrinsics.v) or
a circuit_directory/filelist.txt (e.g. ch_intrinsics/filelist.txt). filelist.txt would specify the names of the source hdl files, within that directory. The circuit name would be given by the circuit_directory in this case, and that would be the default name for the output files etc.
I am not sure how Odin-II would handle this; I believe it can already take a list of files, in which case this wouldn't require changes to Odin-II. @sdamghan : can you confirm that?
Current Behaviour
Right now, after a benchmark circuit is created (usually in multiple hdl files) they have to all be concatenated into one big file before putting into the vtr regtest/qor suites. That makes the benchmark structure less than ideal if we want to later change it more.
Possible Solution
See above.
Context
Having to concatenate everything hasn't caused huge problems, but it is annoying if the design is "live" and being modified by a developer rather than just used to test the CAD tools.
The text was updated successfully, but these errors were encountered:
This issue has been inactive for a year and has been marked as stale. It will be closed in 15 days if it continues to be stale. If you believe this is still an issue, please add a comment.
I think this would be good to discuss at a future VTR meeting ... re-opening and put @AlexandreSinger and @jgoeders as owners for now so we can discuss.
Right now the script infrastructure for regtests, running suites of designs etc. in vtr assumes each benchmark consists of one file. We're slightly weakening that by allowing .vh include files, but it would be good to allow benchmarks to include an arbitrary list of files as that is usually how they are created. Right now we have to concatenate all the hdl into one big file, purely for script convenience.
Proposed Behaviour
Allow run_vtr_task, run_vtr_flow and config.txt to all take an argument of either:
Current Behaviour
Right now, after a benchmark circuit is created (usually in multiple hdl files) they have to all be concatenated into one big file before putting into the vtr regtest/qor suites. That makes the benchmark structure less than ideal if we want to later change it more.
Possible Solution
See above.
Context
Having to concatenate everything hasn't caused huge problems, but it is annoying if the design is "live" and being modified by a developer rather than just used to test the CAD tools.
The text was updated successfully, but these errors were encountered: