-
Notifications
You must be signed in to change notification settings - Fork 758
Arm backend: Refactor compile spec handling #14111
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/14111
Note: Links to docs will display an error until the docs builds have been completed. ⏳ No Failures, 3 PendingAs of commit 89e07db with merge base 245630a ( This comment was automatically generated by Dr. CI and updates every 15 minutes. |
|
test fails are unrelated |
|
@Erik-Lundell this seem to need a rebase :( Sorry about that. |
Keep compile spec in easily handled ArmCompileSpec format as long as possible, only go to list[CompileSpec] format when neccessary for the backend API. ArmCompileSpec is subclassed for each backend to minimize risk of using incorrect compile spec for a specific target. TODO: go back to ArmCompileSpec format in our backend classes. Signed-off-by: Erik Lundell <[email protected]> Change-Id: I90f6e7bc8cbfd5d248da728f401c8ae1fc116dab
b144f60 to
89e07db
Compare
| @@ -1,245 +0,0 @@ | |||
| # Copyright 2023-2025 Arm Limited and/or its affiliates. | |||
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.
the buck files need to be updated to reflect this deletion.
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.
looks like there are also references in docs/
This reverts commit 29cec35. This broke our internal Buck builds and I think revert/reapply will allow us to ingest changes faster overall. (Have plans to get some Buck coverage in GitHub CI that will prevent problems like this going forward soon.) ghstack-source-id: 0688ea4 ghstack-comment-id: 3276337046 Pull-Request: #14175
This reverts commit 29cec35. This broke our internal Buck builds and I think revert/reapply will allow us to ingest changes faster overall. (Have plans to get some Buck coverage in GitHub CI that will prevent problems like this going forward soon.) ghstack-source-id: ee95d6e ghstack-comment-id: 3276337046 Pull-Request: #14175
This reverts commit 29cec35. This broke our internal Buck builds and I think revert/reapply will allow us to ingest changes faster overall. (Have plans to get some Buck coverage in GitHub CI that will prevent problems like this going forward soon.)
Summary: Redoing pytorch#14111 with additional fixes Differential Revision: D82171193
Summary: Pull Request resolved: pytorch#14191 Redoing pytorch#14111 with additional fixes Differential Revision: D82171193
Summary: Pull Request resolved: pytorch#14191 Redoing pytorch#14111 with additional fixes Differential Revision: D82171193
Summary: Pull Request resolved: pytorch#14191 Redoing pytorch#14111 with additional fixes Differential Revision: D82171193
Summary: Pull Request resolved: pytorch#14191 Redoing pytorch#14111 with additional fixes Differential Revision: D82171193
Summary: Pull Request resolved: pytorch#14191 Redoing pytorch#14111 with additional fixes Differential Revision: D82171193
Summary: Pull Request resolved: pytorch#14191 Redoing pytorch#14111 with additional fixes Differential Revision: D82171193
Summary: Pull Request resolved: pytorch#14191 Redoing pytorch#14111 with additional fixes Differential Revision: D82171193
Summary: Pull Request resolved: pytorch#14191 Redoing pytorch#14111 with additional fixes Reviewed By: digantdesai Differential Revision: D82171193
Summary: Pull Request resolved: pytorch#14191 Redoing pytorch#14111 with additional fixes Reviewed By: digantdesai Differential Revision: D82171193
Summary: Pull Request resolved: pytorch#14191 Redoing pytorch#14111 with additional fixes Reviewed By: digantdesai Differential Revision: D82171193
Summary: Redoing pytorch#14111 with additional fixes Reviewed By: digantdesai Differential Revision: D82171193
Summary: Redoing #14111 with additional fixes Differential Revision: D82171193 cc @digantdesai @freddan80 @per @zingo @oscarandersson8218
…#14145)" (pytorch#14174) This reverts commit 8c51641. Trying to revert pytorch#14111 and this has conflicts.
…ytorch#14175) This reverts commit 29cec35. This broke our internal Buck builds and I think revert/reapply will allow us to ingest changes faster overall. (Have plans to get some Buck coverage in GitHub CI that will prevent problems like this going forward soon.)
Summary: Redoing pytorch#14111 with additional fixes Differential Revision: D82171193 cc @digantdesai @freddan80 @per @zingo @oscarandersson8218
Instead of factories to create list[CompileSpec], use a dataclass that contains all specs directly. This cleans up the API for creating CompileSpecs and aligns it with how the partitioner and quantizer is designed. Keep compile spec in easily handled ArmCompileSpec format as long as possible, only go to list[CompileSpec] format when neccessary for the backend API. ArmCompileSpec is subclassed for each backend to minimize risk of using incorrect compile spec for a specific target.
cc @digantdesai @freddan80 @per @zingo @oscarandersson8218