Skip to content

Update PostponeDequantizeOpBelowUseChainPass cost model (#22813) - #22813

Open
DrJessop wants to merge 1 commit into
pytorch:mainfrom
DrJessop:export-D119727954
Open

DrJessop wants to merge 1 commit into
pytorch:mainfrom
DrJessop:export-D119727954

Conversation

@DrJessop

@DrJessop DrJessop commented Sep 14, 2026

Copy link
Copy Markdown
Contributor

Summary:

If we move a dequant down and it happens to be right above a quant, there should be no additional cost incurred by the dequant. That is now reflected in the cost model.

Reviewed By: ethansfng

Differential Revision: D119727954

@pytorch-bot

pytorch-bot Bot commented Sep 14, 2026

Copy link
Copy Markdown

🔗 Helpful Links

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

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

⏳ No Failures, 5 Pending

As of commit 43b5337 with merge base b6aed42 (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 Sep 14, 2026
@meta-codesync

meta-codesync Bot commented Sep 14, 2026

Copy link
Copy Markdown
Contributor

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

@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.

Summary:

If we move a dequant down and it happens to be right above a quant, there should be no additional cost incurred by the dequant. That is now reflected in the cost model.

Reviewed By: ethansfng

Differential Revision: D119727954
@meta-codesync meta-codesync Bot changed the title Update PostponeDequantizeOpBelowUseChainPass cost model Update PostponeDequantizeOpBelowUseChainPass cost model (#22813) Sep 15, 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. meta-exported

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants