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
core: Fix terminator conditions for unregistered operations #1201
Conversation
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## main #1201 +/- ##
=======================================
Coverage 88.71% 88.71%
=======================================
Files 166 166
Lines 22855 22858 +3
Branches 3478 3479 +1
=======================================
+ Hits 20275 20278 +3
Misses 2025 2025
Partials 555 555
☔ View full report in Codecov by Sentry. |
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!
I just pushed #1202, which should move the allow_unregistered
to the MLContext
. This means that if allow_unregistered
is not set, then we cannot create UnregisteredOp
in the first place, so we don't have to pass this argument to verify
anymore.
d4e7e01
to
ac2a8ee
Compare
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.
Perfect, thanks a lot!
This PR refines terminator conditions for unregistered operations.
Namely, if we allow unregistered operations, then their terminator conditions are implicitly fulfilled.
It also modifies
has_trait
to assume the existence of any trait for unregistered operations.This is modelled after the
mayBeValidWithoutTerminator
andmightHaveTrait
in MLIR.Resolves #1167