Add support for SystemVerilog, and allow passing additional arguments to verilator #11
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Recently discovered this library and started integrating into my workflow and I've absolutely loved it, but noticed a few features that were lacking and added them in:
SystemVerilog support - The
build
function was hardcoded to only allow ".v" files, added ".sv" as well to allow for top-level files to be SystemVerilog (of which a sufficient subset is supported in Verilator that using SystemVerilog files with Verilator is not uncommon).Allow parameter overrides - Some of my tests passed parameters into the top-level module to allow testing the module under different conditions, so
build
now takes a parameters dict object that is converted into-G
flags and passed to verilator.Allow passing additional custom arguments to verilator at build time.