-
Notifications
You must be signed in to change notification settings - Fork 77
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
interactive: AvailablePass now has either a pass type or instance, no spec #3725
Conversation
data=(type(value), value.pipeline_pass_spec()) | ||
if isinstance(value, ModulePass) | ||
else (value, None), |
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.
This is a newly introduced ugly bit due to the tree node data still being in terms of pass type and spec, next PR will remove this.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #3725 +/- ##
==========================================
- Coverage 91.28% 91.28% -0.01%
==========================================
Files 468 468
Lines 58605 58601 -4
Branches 5656 5656
==========================================
- Hits 53496 53492 -4
Misses 3659 3659
Partials 1450 1450 ☔ View full report in Codecov by Sentry. |
@@ -82,25 +81,15 @@ def test_get_all_available_passes(): | |||
( | |||
AvailablePass( | |||
display_name="bc", | |||
module_pass=BCPass, | |||
pass_spec=None, | |||
module_pass=BCPass(), |
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.
nit: It looks like AvailablePass can still be built with a type?
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.
Yep, this is used when "Condense Mode" is not on, and for mlir-opt pass as we want to present the pass as an option to the user without instantiating it
Same deal as #3723, we used to need the spec due to potential mutability, now don't need it.