New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
import package is broken under multiply instantiated cells #542
Comments
Original Redmine Comment Sorry this works for me, please give a failing example in verilator test_regress format. |
Original Redmine Comment It looks like the reason for this issue is that verilator does not try to find/open a file with the name driver_definitions.sv, as it used to do (or as VCS does). So, I get an error when I try to compile just this module:
If I add:
then it works. Similarly, test_regress/t/t_package_abs.v has package definition in the same file, not in a separate file as it is usually done. |
Original Redmine Comment No, verilator has never implemented automatic package resolution, and it fails on both revisions the same. Also neither does VCS. At present VCS requires all packages to be listed on the command line, or equivalently in a file included off from the command line. Even `including a package from a module that is found by automatic library lookup is NOT sufficient. About 3 months ago I had a long debate with them on getting them to fix this mess but they stonewalled. Yes, it should be obvious that this is useful.... Anyhow if you can isolate the test case that passes on the old rev and fails now I'll fix it; there is a lot changed there and I have little doubt that something was broken. |
Original Redmine Comment You are right - it is not an include issue. Here is reduced test case:
Latest verilator version:
Older version:
Note that 3.833 includes tri-state fixes. |
Original Redmine Comment Fixed in git towards 3.841. |
Original Redmine Comment In 3.841. |
Author Name: Alex Solomatnikov
Original Redmine Issue: 542 from https://www.veripool.org
Original Date: 2012-08-07
Original Assignee: Wilson Snyder (@wsnyder)
This used to work 3 months ago:
Now I get errors:
The text was updated successfully, but these errors were encountered: