Skip to content

Arm backend: Add 6D tensor and pixel shuffle/unshuffle support#14854

Closed
pytorchbot wants to merge 2 commits intorelease/1.0from
cherry-pick-14626-by-pytorch_bot_bot_
Closed

Arm backend: Add 6D tensor and pixel shuffle/unshuffle support#14854
pytorchbot wants to merge 2 commits intorelease/1.0from
cherry-pick-14626-by-pytorch_bot_bot_

Conversation

@pytorchbot
Copy link
Collaborator

Adds 6D tensor support required by pixel_shuffle/pixel_unshuffle when given 4D inputs, which means for now we only support 4D inputs. Adds TOSA, VGF and xfailing Ethos-U85 unit tests.

cc @digantdesai @freddan80 @per @zingo @oscarandersson8218

Adds 6D tensor support required by pixel_shuffle/pixel_unshuffle when
given 4D inputs, which means for now we only support 4D inputs. Adds
TOSA, VGF and xfailing Ethos-U85 unit tests.

cc @digantdesai @freddan80 @per @zingo @oscarandersson8218

(cherry picked from commit 6e7353f)
@pytorch-bot
Copy link

pytorch-bot bot commented Oct 7, 2025

🔗 Helpful Links

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

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

❌ 4 New Failures, 2 Cancelled Jobs, 4 Unrelated Failures

As of commit 0300e22 with merge base e0dda90 (image):

NEW FAILURES - The following jobs have failed:

CANCELLED JOBS - The following jobs were cancelled. Please retry:

FLAKY - The following jobs failed but were likely due to flakiness present on trunk:

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

@meta-cla meta-cla 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 Oct 7, 2025
@GregoryComer
Copy link
Member

@digantdesai It looks like there are some issues with the cherry-pick. Can you help fix the PR? It will likely need a maintainer to push changes to the PR branch, so I don't think the ARM engineers can do it. Thanks.

@mansnils
Copy link
Collaborator

@digantdesai It looks like there are some issues with the cherry-pick. Can you help fix the PR? It will likely need a maintainer to push changes to the PR branch, so I don't think the ARM engineers can do it. Thanks.

If we for some reason can't get it into 1.0 branch, I think that is ok. It is nice to have but not absolutely needed.

@digantdesai
Copy link
Contributor

Can you help fix the PR?

seems like mypy? let me try..rebasing first.

@digantdesai
Copy link
Contributor

Drop this?

@github-actions
Copy link

Looks like this PR hasn't been updated in a while so we're going to go ahead and mark this as Stale.
Feel free to remove the Stale label if you feel this was a mistake.
If you are unable to remove the Stale label please contact a maintainer in order to do so.
If you want the bot to never mark this PR stale again, add the no-stale label.
Stale pull requests will automatically be closed after 30 days of inactivity.

@github-actions github-actions bot added the stale PRs inactive for over 60 days label Dec 21, 2025
@Sebastian-Larsson Sebastian-Larsson added the partner: arm For backend delegation, kernels, demo, etc. from the 3rd-party partner, Arm label Feb 11, 2026
@zingo
Copy link
Collaborator

zingo commented Feb 11, 2026

As 1.0 in closed and 1.1 i out lets close this

@zingo zingo closed this Feb 11, 2026
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. partner: arm For backend delegation, kernels, demo, etc. from the 3rd-party partner, Arm stale PRs inactive for over 60 days

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants