-
Notifications
You must be signed in to change notification settings - Fork 298
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
[Calyx to FSM]Fix the bug when calyx multi-component design lower to fsm. #5341
Conversation
@rachitnigam 😃Hi, I have found the problem and fixed it. |
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.
Nice, thanks for working on this! I think this solution makes sense. @mortbopet I believe you initially implemented this. Any concerns?
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.
Makes sense to me, thank you for finding and fixing the bug!
@mikeurbach Thank you!I remember that you answered my question last year.:smiley: |
@mikeurbach @mortbopet I should modify the test case again. |
@linuxlonelyeagle looks like some tests will need to be updated. For example, this name will need to be updated:
You can run the tests with |
Thank you. |
I have modified the test and run
|
Great. Assuming the tests pass in CI I will merge it. |
Awesome, thanks for fixing this @linuxlonelyeagle |
I found this problem while learning circt during this time, and I have solved it.You can see it here.The names of the state machines generated in the calyx-to-fsm pass are all called control. This leads to a problem when designing with multiple components, where components may instantiate the state machines of other components.