-
-
Notifications
You must be signed in to change notification settings - Fork 48
🐛 Fix CtrlOp::getBodyUnitary() for operations with parameters #1464
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
base: main
Are you sure you want to change the base?
Conversation
📝 WalkthroughWalkthroughUpdated CHANGELOG.md with PR Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Codecov Report❌ Patch coverage is
📢 Thoughts on this report? Let us know! |
Description
While debugging test cases in #1426, I finally figured out why
CtrlOp::getBodyUnitary()sometimes returned an invalidUnitaryOpInterface.Whenever an operation has at least one parameter, the first operation in the modifier's body will be a
arith.constantand not the unitary operation like it is currently assumed in the function.This PR resolves this by iterating over all operations in the body and only returning when the first
UnitaryOpInterfaceoperation has been found or there is none.It affects all
crx,crzz,cu, ... operations.Required for #1426
Checklist: