Skip to content
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

Feature - checking of modport directions in interfaces #1110

Closed
veripoolbot opened this issue Nov 15, 2016 · 3 comments
Closed

Feature - checking of modport directions in interfaces #1110

veripoolbot opened this issue Nov 15, 2016 · 3 comments
Assignees
Labels
area: lint Issue involves SystemVerilog lint checking resolution: fixed Closed; fixed

Comments

@veripoolbot
Copy link
Contributor


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.

@veripoolbot
Copy link
Contributor Author


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.

@veripoolbot
Copy link
Contributor Author


Original Redmine Comment
Author Name: Wilson Snyder (@wsnyder)
Original Date: 2017-11-18T22:52:29Z


Fixed in git towards 3.915.

@veripoolbot
Copy link
Contributor Author


Original Redmine Comment
Author Name: Wilson Snyder (@wsnyder)
Original Date: 2017-11-25T20:48:06Z


In 3.916.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: lint Issue involves SystemVerilog lint checking resolution: fixed Closed; fixed
Projects
None yet
Development

No branches or pull requests

2 participants