-
Notifications
You must be signed in to change notification settings - Fork 746
Arm backend: Sort passes in _tosa_pipeline into blocks #15637
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/15637
Note: Links to docs will display an error until the docs builds have been completed. ❌ 1 New Failure, 1 Cancelled Job, 3 Unrelated FailuresAs of commit 7df244d with merge base 80c9040 ( NEW FAILURE - The following job has failed:
CANCELLED JOB - The following job was cancelled. Please retry:
BROKEN TRUNK - The following jobs failed but were present on the merge base:👉 Rebase onto the `viable/strict` branch to avoid these failures
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
|
@pytorchbot label "partner: arm" |
|
@pytorchbot label ciflow/trunk |
|
Feel free to add me as reviewer. @digantdesai is OOO. |
The passes listed in `ArmPassManager._tosa_pipeline` can feel a bit arbitrary because there is no clearly intended structure or pattern being applied there. Restructure the list into clearly labelled blocks to make the code easier to read and maintain. Signed-off-by: Martin Lindström <[email protected]> Change-Id: Iadf37cda2c7a88cad80bf363062d38d492206be7
ba79dc1 to
7df244d
Compare
|
Fails are unrelated |
|
All changes are within the same file no buck2 build file should be changed. |
The passes listed in
ArmPassManager._tosa_pipelinecan feel a bit arbitrary because there is no clearly intended structure or pattern being applied there. Restructure the list into clearly labelled blocks to make the code easier to read and maintain.cc @freddan80 @per @zingo @oscarandersson8218 @digantdesai