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
Ideally, I'd like to run something like t_dpi_import with and without --dpi-hdr-only (to two different output directories). Then I'd check to make sure that with the flag, the DPI header is the only thing that comes out and make sure it is the same as the file produced without the flag. I'm not sure if driver.pl will support something like this. I need to do some reading to figure that out, but if there are other suggestions for testing I'm all ears.
The text was updated successfully, but these errors were encountered:
Original Redmine Comment
Author Name: Wilson Snyder (@wsnyder)
Original Date: 2019-08-27T23:02:00Z
I'm fine with your squashing and pushing this.
However in the larger picture (perhaps worth discussing in the other bug) I'd prefer we not need to run the generation of the dpi headers as a separate step.
Author Name: Todd Strader (@toddstrader)
Original Redmine Issue: 1491 from https://www.veripool.org
Original Assignee: Todd Strader (@toddstrader)
Towards #�. I have the feature coded, but am not sure about the best way to test this:
https://github.com/toddstrader/verilator-dev/tree/dpi-header
Ideally, I'd like to run something like t_dpi_import with and without --dpi-hdr-only (to two different output directories). Then I'd check to make sure that with the flag, the DPI header is the only thing that comes out and make sure it is the same as the file produced without the flag. I'm not sure if driver.pl will support something like this. I need to do some reading to figure that out, but if there are other suggestions for testing I'm all ears.
The text was updated successfully, but these errors were encountered: