Skip to content

[ET-VK][ez] Update requirements for partitioning to_dim_order_copy #7949

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

Merged
merged 1 commit into from
Jan 24, 2025

Conversation

pytorchbot
Copy link
Collaborator

This PR was created by the merge bot to help merge the original PR into the main branch.
ghstack PR number: #7859
^ Please use this as the source of truth for the PR details, comments, and reviews
ghstack PR base: https://github.com/pytorch/executorch/tree/gh/SS-JIA/171/base
ghstack PR head: https://github.com/pytorch/executorch/tree/gh/SS-JIA/171/head
Merge bot PR base: https://github.com/pytorch/executorch/tree/main
Merge bot PR head: https://github.com/pytorch/executorch/tree/gh/SS-JIA/171/orig
@diff-train-skip-merge

Pull Request resolved: #7859

## Context

The previous registration of the to dim order copy op is incorrect. Currently, there is no implementation for the op in the Vulkan backend, but since Vulkan manages memory layout internally the op node can be removed as long as the only thing being changed is dim order.

In some instances the op can be used to modify the dtype, in which case it will not be removed and the Vulkan delegate cannot execute the op correctly. Therefore, update the registration of the op to reflect this restriction.

This diff should unblock enabling dim order ops for Vulkan.
ghstack-source-id: 262710507
@exported-using-ghexport

Differential Revision: [D68528213](https://our.internmc.facebook.com/intern/diff/D68528213/)

Co-authored-by: Stephen Jia <[email protected]>
(cherry picked from commit 5ee5f2f)
Copy link

pytorch-bot bot commented Jan 24, 2025

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/7949

Note: Links to docs will display an error until the docs builds have been completed.

✅ No Failures

As of commit 7188c7a with merge base 9069017 (image):
💚 Looks good so far! There are no failures yet. 💚

This comment was automatically generated by Dr. CI and updates every 15 minutes.

@facebook-github-bot facebook-github-bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Jan 24, 2025
@SS-JIA SS-JIA merged commit 7c16c49 into release/0.5 Jan 24, 2025
42 checks passed
@SS-JIA SS-JIA deleted the cherry-pick-7896-by-pytorch_bot_bot_ branch January 24, 2025 21:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants