-
Notifications
You must be signed in to change notification settings - Fork 92
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
AUTOINST problem for module containing clocking block #1313
Comments
Original Redmine Comment There is some code in place to skip over the clocking. Can you attach a self-contained test? Thanks. |
Original Redmine Comment Before expansion:
After expansion:
Also, note that the indentation is messed up for the clocking block. David |
Original Redmine Comment I made a stab at this but it needs more time as broke clocking modports. Basically the parser needs to change to understand "default clocking foo;" does not start a declaration, but "default clocking foo @(...);" does. |
Original Redmine Comment Hi Wilson. I just hit this problem again and wondered if there's been any activity on it during the past year. Thanks, David |
Author Name: David Rogoff
Original Redmine Issue: 1313 from https://www.veripool.org
I just created a simple clock/reset module to instantiate in my testbench. The module contains a clocking block:
When I instantiated the module and expanded it, it added
Looks like the input and output keywords in the default line are confusing AUTOINST.
Easy fix?
Thanks,
David
The text was updated successfully, but these errors were encountered: