-
Notifications
You must be signed in to change notification settings - Fork 309
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
[LoopScheduleToCalyx] deduplicate groups within a ParOp. #8055
Conversation
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.
I think this makes sense as a canonicalization, but is the error avoided with the change in LoopScheduleToCalyx? In general, I think we strive for a world where the canonicalizations are not required for success / correctness.
It is not, that change avoids a use after free issue. I have not totally fixed the error yet though so going back to draft mode. (Edit: I agree with your sentiment. I'll follow up later) |
@mikeurbach I've updated this so that canonicalization isn't used as an "operation fixer-upper". |
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.
awesome, thanks for that. looks good to me.
Thanks! This is branched off #8048 so if you have a chance to review that, it'd be great :-) |
Deduplicates multiple occurrences of the same Enable in a
ParOp
. This can be introduced automatically by a compiler lowering phase, so we add this as a canonicalization pattern. Additionally, ensures that the pipeline register (and not the pipeline stage) is used in Calyx computation assignments.Fixes #8050.