We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Author Name: Todd Strader (@toddstrader) Original Redmine Issue: 985 from https://www.veripool.org Original Date: 2015-10-28 Original Assignee: Wilson Snyder (@wsnyder)
https://github.com/toddstrader/verilator-dev/tree/missing_intf_msg
When an interface with no definition is connected to a module, you get this:
%Error: Internal Error: t/t_missing_interface_bad.v:16: ../V3LinkDot.cpp:375: Unlinked interface
As opposed to this, which you get if the interface is not connected to a module:
%Error: t/t_missing_interface_bad.v:23: Cannot find file containing module: foo_intf
I think the latter should appear in both cases.
The text was updated successfully, but these errors were encountered:
Original Redmine Comment Author Name: Wilson Snyder (@wsnyder) Original Date: 2015-10-30T01:45:03Z
Fair enough, thanks for the test. Fixed in git towards 3.878.
Sorry, something went wrong.
Original Redmine Comment Author Name: Wilson Snyder (@wsnyder) Original Date: 2015-11-01T13:23:52Z
In 3.878.
wsnyder
No branches or pull requests
Author Name: Todd Strader (@toddstrader)
Original Redmine Issue: 985 from https://www.veripool.org
Original Date: 2015-10-28
Original Assignee: Wilson Snyder (@wsnyder)
https://github.com/toddstrader/verilator-dev/tree/missing_intf_msg
When an interface with no definition is connected to a module, you get this:
As opposed to this, which you get if the interface is not connected to a module:
I think the latter should appear in both cases.
The text was updated successfully, but these errors were encountered: