Skip to content

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

Merged
merged 2 commits into from
Mar 25, 2024

Conversation

tpwrules
Copy link
Contributor

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.

@tpwrules tpwrules requested a review from whitequark as a code owner March 23, 2024 17:58
Copy link

codecov bot commented Mar 23, 2024

Codecov Report

Attention: Patch coverage is 95.23810% with 1 lines in your changes are missing coverage. Please review.

Project coverage is 89.87%. Comparing base (6ffafef) to head (eb0fe16).

Files Patch % Lines
amaranth/sim/core.py 88.88% 0 Missing and 1 partial ⚠️
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.
📢 Have feedback on the report? Share it here.

Copy link
Member

@whitequark whitequark left a 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)
@tpwrules tpwrules changed the title Allow name of "" to denote a private Signal Allow Signals to be privately named using name="" Mar 25, 2024
Copy link
Member

@whitequark whitequark left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks a lot!

@whitequark whitequark added this pull request to the merge queue Mar 25, 2024
Merged via the queue into amaranth-lang:main with commit fa2adbe Mar 25, 2024
20 checks passed
@tpwrules tpwrules deleted the private-names branch March 25, 2024 20:10
@whitequark whitequark added this to the 0.5 milestone Apr 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

Signals with private names
3 participants