-
Notifications
You must be signed in to change notification settings - Fork 734
Move user-defined passes after SpecPropPass #15932
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
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/15932
Note: Links to docs will display an error until the docs builds have been completed. This comment was automatically generated by Dr. CI and updates every 15 minutes. |
dee69c9 to
bd92f7a
Compare
This PR needs a
|
JacobSzwejbka
left a comment
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.
Review automatically exported from Phabricator review in Meta.
Summary: 1. Use `ExecutorchBackendConfig` instead of inserting the pass. 2. Move SpecPropPass after user-defined passes. It was originally swapped here: D80840528. cc ethansfng, who has a pass that should run before SpecPropPass Reviewed By: JacobSzwejbka, larryliu0820 Differential Revision: D87576772
bd92f7a to
6fd9ac3
Compare
Summary: 1. Use `ExecutorchBackendConfig` instead of inserting the pass. 2. Move SpecPropPass after user-defined passes. It was originally swapped here: D80840528. cc ethansfng, who has a pass that should run before SpecPropPass Reviewed By: JacobSzwejbka, larryliu0820 Differential Revision: D87576772
6fd9ac3 to
3f1632c
Compare
Summary:
ExecutorchBackendConfiginstead of inserting the pass.Differential Revision: D87576772