Skip to content

[slimtensor] integration into backend#17070

Merged
Gasoonjia merged 1 commit intomainfrom
gh/gasoonjia/101/orig
Jan 30, 2026
Merged

[slimtensor] integration into backend#17070
Gasoonjia merged 1 commit intomainfrom
gh/gasoonjia/101/orig

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: #16565 by @Gasoonjia
^ 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/gasoonjia/101/base
ghstack PR head: https://github.com/pytorch/executorch/tree/gh/gasoonjia/101/head
Merge bot PR base: https://github.com/pytorch/executorch/tree/main
Merge bot PR head: https://github.com/pytorch/executorch/tree/gh/gasoonjia/101/orig
Differential Revision: D90606409
@diff-train-skip-merge

Pull Request resolved: #16565

This diff makes cuda backend actually use slimtensor.

It:
1. updates cuda_backends to create slimtensor from given etensor
2. removed duplicate etensor-driven shim layers under cuda_backend
3. update cmake logic in both cuda backend and aoti backend

Perf maintains the same. Shows as before.
 {F1984982156}

Worth to notice that currently we keeps two sets of common shims, one is etensor-based and for metal backend, the other is slimtensor-based which used by cuda backend, to not impact metal backend work.

When Metal backend finishs the migration, we should delete the duplicate common shims and only keep slimtensor-based one.

ghstack-source-id: 336976428
@exported-using-ghexport

Differential Revision: [D90606409](https://our.internmc.facebook.com/intern/diff/D90606409/)
@pytorch-bot
Copy link

pytorch-bot bot commented Jan 30, 2026

🔗 Helpful Links

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

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

❌ 1 Cancelled Job, 98 Pending, 1 Unrelated Failure

As of commit 01fd060 with merge base 1df4dac (image):

CANCELLED JOB - The following job was cancelled. Please retry:

FLAKY - The following job failed but was 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 Jan 30, 2026
@github-actions
Copy link

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.

@Gasoonjia Gasoonjia merged commit 9d257c8 into main Jan 30, 2026
162 of 170 checks passed
@Gasoonjia Gasoonjia deleted the gh/gasoonjia/101/orig branch January 30, 2026 18:54
larryliu0820 pushed a commit that referenced this pull request Feb 2, 2026
This PR was created by the merge bot to help merge the original PR into
the main branch.
ghstack PR number: #16565 by
@Gasoonjia
^ 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/gasoonjia/101/base
ghstack PR head:
https://github.com/pytorch/executorch/tree/gh/gasoonjia/101/head
Merge bot PR base: https://github.com/pytorch/executorch/tree/main
Merge bot PR head:
https://github.com/pytorch/executorch/tree/gh/gasoonjia/101/orig
Differential Revision:
[D90606409](https://our.internmc.facebook.com/intern/diff/D90606409/)
@diff-train-skip-merge

Co-authored-by: gasoonjia <gasoonjia@icloud.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
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.

2 participants

Comments