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

Jump to bottom

AUTOINSTPARAM work for interfaces? #1100

Closed
veripoolbot opened this issue Oct 31, 2016 · 2 comments
Closed

AUTOINSTPARAM work for interfaces? #1100

veripoolbot opened this issue Oct 31, 2016 · 2 comments
Assignees
@wsnyder
Labels
autos

Comments

@veripoolbot
Copy link
Collaborator

Author Name: David Rogoff
Original Redmine Issue: 1100 from https://www.veripool.org

Original Assignee: Wilson Snyder (@wsnyder)

Hi.

As usual, thanks for keeping verilog-mode going!

Question: I see that AUTOINST works for the ports of an instantiated SV interface but AUTOINSTPARAM doesn't appear to get expanded. Can this be easily fixed?

Thanks,

David
@veripoolbot
Copy link
Collaborator Author

Original Redmine Comment
Author Name: Wilson Snyder (@wsnyder)
Original Date: 2016-10-31T17:15:27Z

I know what you mean, but would you mind contributing a test showing the expected behavior? Thanks.

@veripoolbot
Copy link
Collaborator Author

Original Redmine Comment
Author Name: David Rogoff
Original Date: 2016-10-31T17:46:53Z

Wilson Snyder wrote:

I know what you mean, but would you mind contributing a test showing the expected behavior? Thanks.

Sorry - it does work. My interface file left out the keyword "parameter" in the interface definition. I guess the tools assume that like they assume "input" on task arguments. However, verilog-mode needs it and works fine when I put it in.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@wsnyder wsnyder

Labels
autos
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@wsnyder @veripoolbot