Skip to content

[ET-VK] Adding repeat support to add_copy_packed_dim_offset_node function. #9721

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
Mar 27, 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: #9414 by @trivedivivek
^ 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/trivedivivek/67/base
ghstack PR head: https://github.com/pytorch/executorch/tree/gh/trivedivivek/67/head
Merge bot PR base: https://github.com/pytorch/executorch/tree/main
Merge bot PR head: https://github.com/pytorch/executorch/tree/gh/trivedivivek/67/orig
@diff-train-skip-merge

…tion.

Pull Request resolved: #9414

This diff adds support for the repeat operation in `add_copy_packed_dim_offset_node` function in the Vulkan backend for Executorch. The function now takes an additional boolean parameter, "repeat", which indicates whether the copy should wrap around the tensor dimension.

`copy_packed_dim_offset` shader now has 2 functions `repeat_copy` and `no_repeat_copy` which are chosen based on specialization constant parameter.
`no_repeat_copy` function has the legacy copy code.
`repeat_copy` function reads input tensor's dim based on output pos and wraps it according to WHCB repetitions.

Push constants `src_offset` and `dst_offset` contains source and destination's WHCB dimensions (and not copy offsets) respectively, when calling repeat function.
ghstack-source-id: 274452675
@exported-using-ghexport

Differential Revision: [D71477552](https://our.internmc.facebook.com/intern/diff/D71477552/)
@pytorchbot pytorchbot requested a review from SS-JIA as a code owner March 27, 2025 16:24
Copy link

pytorch-bot bot commented Mar 27, 2025

🔗 Helpful Links

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

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

⏳ No Failures, 5 Pending

As of commit e804f7b with merge base 976fe48 (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 Mar 27, 2025
@kirklandsign kirklandsign merged commit 565b2b4 into main Mar 27, 2025
81 of 83 checks passed
@kirklandsign kirklandsign deleted the gh/trivedivivek/67/orig branch March 27, 2025 17:12
kirklandsign pushed a commit that referenced this pull request Apr 11, 2025
…tion. (#9721)

This diff adds support for the repeat operation in `add_copy_packed_dim_offset_node` function in the Vulkan backend for Executorch. The function now takes an additional boolean parameter, "repeat", which indicates whether the copy should wrap around the tensor dimension.

`copy_packed_dim_offset` shader now has 2 functions `repeat_copy` and `no_repeat_copy` which are chosen based on specialization constant parameter.
`no_repeat_copy` function has the legacy copy code.
`repeat_copy` function reads input tensor's dim based on output pos and wraps it according to WHCB repetitions.

Push constants `src_offset` and `dst_offset` contains source and destination's WHCB dimensions (and not copy offsets) respectively, when calling repeat function.

Differential Revision: [D71477552](https://our.internmc.facebook.com/intern/diff/D71477552/)
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. topic: not user facing
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants