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

Module and signal names can collide in illegal ways in generated SystemVerilog #205

Closed
mkorbel1 opened this issue Nov 22, 2022 · 0 comments · Fixed by #207
Closed

Module and signal names can collide in illegal ways in generated SystemVerilog #205

mkorbel1 opened this issue Nov 22, 2022 · 0 comments · Fixed by #207
Labels
bug Something isn't working

Comments

@mkorbel1
Copy link
Contributor

Describe the bug

It is possible to name a signal and a module instance the same thing, but in generated SystemVerilog they cannot be the same. They should be uniquified.

To Reproduce

Create a signal name and module instance name that are the same and generate SystemVerilog

Expected behavior

Names are properly uniquified so that generated SystemVerilog is valid

Actual behavior

Invalid SystemVerilog is generated, leading to a compile time error

Additional: Dart SDK info

No response

Additional: pubspec.yaml

No response

Additional: Context

In a fix, it's important to consider every combination of:

  • input name
  • output name
  • internal signal name
  • module definition name
  • module instance name
@mkorbel1 mkorbel1 added the bug Something isn't working label Nov 22, 2022
mkorbel1 added a commit to mkorbel1/rohd that referenced this issue Nov 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant