Skip to content

Merge back to back slices on the same dim (#19120)#19120

Closed
DrJessop wants to merge 3 commits intopytorch:mainfrom
DrJessop:export-D102278253
Closed

Merge back to back slices on the same dim (#19120)#19120
DrJessop wants to merge 3 commits intopytorch:mainfrom
DrJessop:export-D102278253

Conversation

@DrJessop
Copy link
Copy Markdown
Contributor

@DrJessop DrJessop commented Apr 24, 2026

Summary:

If we have back to back slices on the same dimension, we can remove the top slice and just perform the second one. RemoveOrReplacePassInterface will handle a whole cascade if it exists.

Reviewed By: abeakkas

Differential Revision: D102278253

Summary:
If we have a permute -> unary chain -> mean, based on the reduction dims of the mean, we can either fully remove the preceding permute or move the permute after the mean.

Case 1: Dims after permute are still in same order with respect to each other, we can fully get rid of the permute and just update the reduction dims of the mean.

Case 2: Not case 1. In this case, it's better to move the permute after the mean, since the permute will operate on less data.

Differential Revision: D102268214
@pytorch-bot
Copy link
Copy Markdown

pytorch-bot Bot commented Apr 24, 2026

🔗 Helpful Links

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

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

❗ 1 Active SEVs

There are 1 currently active SEVs. If your PR is affected, please view them below:

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 Apr 24, 2026
@meta-codesync
Copy link
Copy Markdown
Contributor

meta-codesync Bot commented Apr 24, 2026

@DrJessop has exported this pull request. If you are a Meta employee, you can view the originating Diff in D102278253.

@github-actions
Copy link
Copy Markdown

This PR needs a release notes: label

If your change should be included in the release notes (i.e. would users of this library care about this change?), please use a label starting with release notes:. This helps us keep track and include your important work in the next release notes.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "release notes: none"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.

@meta-codesync meta-codesync Bot changed the title Merge back to back slices on the same dim Merge back to back slices on the same dim (#19120) Apr 24, 2026
DrJessop pushed a commit to DrJessop/executorch that referenced this pull request Apr 24, 2026
Summary:
Pull Request resolved: pytorch#19120

If we have back to back slices on the same dimension, we can remove the top slice and just perform the second one.

Differential Revision: D102278253
@DrJessop DrJessop force-pushed the export-D102278253 branch from 18a4c22 to 6c2c50a Compare April 24, 2026 19:39
Summary:
Pull Request resolved: pytorch#19106

I've seen lots of cases where we have a mean followed by a view which can either be fused into mean with keepdim True or False. These views typically become no-ops, however it's nice to remove them if we don't need them. Can potentially make work for later passes easier that are looking for mean, but view in the way.

Differential Revision: D102276633
DrJessop pushed a commit to DrJessop/executorch that referenced this pull request Apr 24, 2026
Summary:
Pull Request resolved: pytorch#19120

If we have back to back slices on the same dimension, we can remove the top slice and just perform the second one. RemoveOrReplacePassInterface will handle a whole cascade if it exists.

Reviewed By: abeakkas

Differential Revision: D102278253
@DrJessop DrJessop force-pushed the export-D102278253 branch from 6c2c50a to 9de0690 Compare April 24, 2026 22:56
DrJessop pushed a commit to DrJessop/executorch that referenced this pull request Apr 24, 2026
Summary:
Pull Request resolved: pytorch#19120

If we have back to back slices on the same dimension, we can remove the top slice and just perform the second one. RemoveOrReplacePassInterface will handle a whole cascade if it exists.

Reviewed By: abeakkas

Differential Revision: D102278253
@DrJessop DrJessop force-pushed the export-D102278253 branch from 9de0690 to ec395b9 Compare April 24, 2026 23:12
DrJessop pushed a commit to DrJessop/executorch that referenced this pull request Apr 24, 2026
Summary:
Pull Request resolved: pytorch#19120

If we have back to back slices on the same dimension, we can remove the top slice and just perform the second one. RemoveOrReplacePassInterface will handle a whole cascade if it exists.

Reviewed By: abeakkas

Differential Revision: D102278253
@DrJessop DrJessop force-pushed the export-D102278253 branch from ec395b9 to fdb522f Compare April 24, 2026 23:19
DrJessop pushed a commit to DrJessop/executorch that referenced this pull request Apr 24, 2026
Summary:
Pull Request resolved: pytorch#19120

If we have back to back slices on the same dimension, we can remove the top slice and just perform the second one. RemoveOrReplacePassInterface will handle a whole cascade if it exists.

Reviewed By: abeakkas

Differential Revision: D102278253
@DrJessop DrJessop force-pushed the export-D102278253 branch from fdb522f to b5504af Compare April 24, 2026 23:24
DrJessop pushed a commit to DrJessop/executorch that referenced this pull request Apr 24, 2026
Summary:
Pull Request resolved: pytorch#19120

If we have back to back slices on the same dimension, we can remove the top slice and just perform the second one. RemoveOrReplacePassInterface will handle a whole cascade if it exists.

Reviewed By: abeakkas

Differential Revision: D102278253
@DrJessop DrJessop force-pushed the export-D102278253 branch from b5504af to 50306b8 Compare April 24, 2026 23:32
DrJessop pushed a commit to DrJessop/executorch that referenced this pull request Apr 24, 2026
Summary:
Pull Request resolved: pytorch#19120

If we have back to back slices on the same dimension, we can remove the top slice and just perform the second one. RemoveOrReplacePassInterface will handle a whole cascade if it exists.

Reviewed By: abeakkas

Differential Revision: D102278253
@DrJessop DrJessop force-pushed the export-D102278253 branch from 50306b8 to 9ad1392 Compare April 24, 2026 23:36
Summary:
Pull Request resolved: pytorch#19120

If we have back to back slices on the same dimension, we can remove the top slice and just perform the second one. RemoveOrReplacePassInterface will handle a whole cascade if it exists.

Reviewed By: abeakkas

Differential Revision: D102278253
@DrJessop DrJessop force-pushed the export-D102278253 branch from 9ad1392 to 9e25e47 Compare April 24, 2026 23:40
@DrJessop DrJessop closed this Apr 24, 2026
DrJessop pushed a commit to DrJessop/executorch that referenced this pull request Apr 24, 2026
Summary:
Pull Request resolved: pytorch#19120

If we have back to back slices on the same dimension, we can remove the top slice and just perform the second one. RemoveOrReplacePassInterface will handle a whole cascade if it exists.

Reviewed By: abeakkas

Differential Revision: D102278253
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. fb-exported meta-exported

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants