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

modport declaration incorrectly treats some outputs as inputs #1246

Closed
veripoolbot opened this issue Nov 28, 2017 · 2 comments
Closed

modport declaration incorrectly treats some outputs as inputs #1246

veripoolbot opened this issue Nov 28, 2017 · 2 comments
Assignees

Comments

@veripoolbot
Copy link

@veripoolbot veripoolbot commented Nov 28, 2017


Author Name: Jeff Bush (@jbush001)
Original Redmine Issue: 1246 from https://www.veripool.org

Original Assignee: Wilson Snyder (@wsnyder)


If you have define multiple outputs in a list within a modport, the first is treated as an output, but subsequent items are not, which (due to fix for bug 1110), causes it to erroneously flag an error. For example, given this:

modport master(output a, b);

a would be marked as an output, but b would not and would flag an error if someone attempted to assign a value to it. I'd expect b to be also treated as an output.

I've attached a test case that reproduces the issue.

@veripoolbot

This comment has been minimized.

Copy link
Author

@veripoolbot veripoolbot commented Nov 29, 2017


Original Redmine Comment
Author Name: Wilson Snyder (@wsnyder)
Original Date: 2017-11-29T00:14:43Z


Simple enough fix, thanks for a complete test case.

Fixed in git towards 3.917.

@veripoolbot

This comment has been minimized.

Copy link
Author

@veripoolbot veripoolbot commented Jan 2, 2018


Original Redmine Comment
Author Name: Wilson Snyder (@wsnyder)
Original Date: 2018-01-02T23:15:25Z


In 3.918.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.