Skip to content

Channels last: preserve metadata across op replacement - #21961

Draft
rascani wants to merge 2 commits into
mainfrom
gh/rascani/7/head
Draft

Channels last: preserve metadata across op replacement#21961
rascani wants to merge 2 commits into
mainfrom
gh/rascani/7/head

Conversation

@rascani

@rascani rascani commented Aug 20, 2026

Copy link
Copy Markdown
Contributor

Preserve complete operator metadata when replacing ATen operators with channels-last dialect counterparts. ExportPass retracing recomputes layout-dependent shape fields while source attribution, quantization annotations, and custom backend metadata survive.

Document that callers must reject or remap semantic metadata tied to dimensions changed by the replacement specification, such as per-channel quantization axes.

pytest -q backends/transforms/test/test_replace_ops_with_channels_last_variants.py (23 passed).

Authored with Codex.

[ghstack-poisoned]
@pytorch-bot

pytorch-bot Bot commented Aug 20, 2026

Copy link
Copy Markdown

🔗 Helpful Links

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

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

✅ No Failures

As of commit 18d7670 with merge base 1b2838b (image):
💚 Looks good so far! There are no failures yet. 💚

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 Aug 20, 2026
@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.

[ghstack-poisoned]
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