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
Support inserting package symbols underneath module symbols #474
Comments
Original Redmine Comment It really should say "unsupported". Currently imports are handled by pulling the symbols into the local module, which isn't proper, but works in most cases. This could be specialized to avoid importing symbols of the same name, but that's still incorrect as the localparam could have a different value inside the package. Therefore package imports need to added as a special scope, or special import cross references, name by name. Note this is broken in Verilog-Perl too; though someone is unlikely to notice unless the conflicting symbol is in one place a data type, and a var in the other. Added t_package_ddecl test to work on later. |
Original Redmine Comment It looks like there is a related problem: localparam defined inside package cannot be used in function defined inside the same package:
I get 2 errors:
The first is on localparam output_clock_as_period = is_period( The second is on for (index = 1; index <= MAX_STRING_LENGTH; index = index + 1) |
Original Redmine Comment Another example:
verilator error:
|
Original Redmine Comment In 3.840. |
Original Redmine Comment Was this issue really fixed? Changes file says about different issue: Fix parameters not supported in constant functions, #�. [Alex Solomatnikov] |
Original Redmine Comment You are right, the bug fixed was part of your test case but not the main point, which remains unresolved. |
Original Redmine Comment This was fixed in 3.844 as part of #�. |
Author Name: Alex Solomatnikov
Original Redmine Issue: 474 from https://www.veripool.org
Original Date: 2012-04-02
Original Assignee: Wilson Snyder (@wsnyder)
Source code line:
Backtrace:
The text was updated successfully, but these errors were encountered: