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: Trevor Elbourne Original Redmine Issue: 1110 from https://www.veripool.org
Original Assignee: Wilson Snyder (@wsnyder)
Verilator currently does not throw an error when driving a signal which is defined to be an input in an interface modport definition.
It would be good if verilator did error in this case, just as it does when a module input port is driven.
The text was updated successfully, but these errors were encountered:
Original Redmine Comment Author Name: Wilson Snyder (@wsnyder) Original Date: 2017-03-21T23:20:49Z
I looked at this when it was filed, and again just now, and it doesn't appear easy.
Sorry, something went wrong.
Original Redmine Comment Author Name: Wilson Snyder (@wsnyder) Original Date: 2017-11-18T22:52:29Z
Fixed in git towards 3.915.
Original Redmine Comment Author Name: Wilson Snyder (@wsnyder) Original Date: 2017-11-25T20:48:06Z
In 3.916.
wsnyder
No branches or pull requests
Author Name: Trevor Elbourne
Original Redmine Issue: 1110 from https://www.veripool.org
Original Assignee: Wilson Snyder (@wsnyder)
Verilator currently does not throw an error when driving a signal which is defined to be an input in an interface modport definition.
It would be good if verilator did error in this case, just as it does when a module input port is driven.
The text was updated successfully, but these errors were encountered: