-
Notifications
You must be signed in to change notification settings - Fork 314
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 ConstantOp Support #7086
Calyx ConstantOp Support #7086
Conversation
I know that LLVM has tools |
4ed164e
to
9bb965b
Compare
9bb965b
to
437693a
Compare
I think before merging this, we need to merge calyxir/calyx#2061. @jiahanxie353 can you get the changes on that resolved so we can move forward with this PR? |
e805fe7
to
0bee621
Compare
Changed the corresponding Calyx Constant Floating Point part reflecting the new changes. Marking it ready for review |
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.
A small few comments, but in general LGTM.
5a48b20
to
963ee19
Compare
Thank you @cgyurgyik ! I have made the changes based on the review. |
Yes once tests pass feel free to merge. Great job! |
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.
LGTM! Eventually we should maybe consider just using the calyx ConstantOp for everything instead of using both the calyx and hw constant ops.
Co-authored-by: Chris Gyurgyik <Gyurgyikcp@gmail.com>
This PR stacks on #6952 and is the first part of #6953 , in which I was asked to break down to smaller patches.
This PR adds support to the creation of Calyx
ConstantOp
in order to support floating point calculation in Calyx. In the meantime, we can support creating a CalyxRegisterOp
by passing in aType
as an argument. I have also included a test case.