-
Notifications
You must be signed in to change notification settings - Fork 178
Allow Signals to be privately named using name=""
#1234
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
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1234 +/- ##
=======================================
Coverage 89.86% 89.87%
=======================================
Files 43 43
Lines 9977 9992 +15
Branches 2409 2417 +8
=======================================
+ Hits 8966 8980 +14
Misses 817 817
- Partials 194 195 +1 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See inline comments.
* Given a private name `$\d+` in RTLIL (as they are not named in the IR) * Not automatically added to VCD files (as they are not named in the IR) * Cannot be traced to a VCD (as they have no name to put in the file) * Cannot be used with an unnamed top-level port (as there is no name)
name=""
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks a lot!
Closes #1223
Tested a couple toy designs. The inclusion of FSM names being private should be enough to prevent regressions.
This does remove a bit of diagnostic power from the FSM tests.