Skip to content

Conversation

@Yuhta
Copy link
Contributor

@Yuhta Yuhta commented Sep 11, 2025

Summary:
The SIMD path is using SLEEF version of pow which is slightly different from std::pow. The fix is to use the same vectorized code (with partial load and store) for the trailing data as well to ensure consistency between results.

Rollback Plan:

Differential Revision: D82265247

@pytorch-bot
Copy link

pytorch-bot bot commented Sep 11, 2025

This appears to be a diff that was exported from phabricator, but the PR author does not have sufficient permissions to run CI. @Yuhta, please do step 2 of internal wiki to get write access so you do not need to get CI approvals in the future. If you think this is a mistake, please contact the Pytorch Dev Infra team.

@linux-foundation-easycla
Copy link

linux-foundation-easycla bot commented Sep 11, 2025

CLA Signed

The committers listed above are authorized under a signed CLA.

  • ✅ login: Yuhta / name: Jimmy Lu (a436877)

@pytorch-bot pytorch-bot bot added the caffe2 label Sep 11, 2025
@pytorch-bot
Copy link

pytorch-bot bot commented Sep 11, 2025

🔗 Helpful Links

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

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

✅ No Failures

As of commit a436877 with merge base 65d642d (image):
💚 Looks good so far! There are no failures yet. 💚

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

@facebook-github-bot
Copy link
Contributor

@Yuhta has exported this pull request. If you are a Meta employee, you can view the originating diff in D82265247.

@facebook-github-bot
Copy link
Contributor

@Yuhta has exported this pull request. If you are a Meta employee, you can view the originating diff in D82265247.

Yuhta added a commit to Yuhta/pytorch that referenced this pull request Sep 12, 2025
…ytorch#162772)

Summary:

The SIMD path is using SLEEF version of `pow` which is slightly
different from `std::pow`.  The fix is to use SLEEF version of `pow` for the
trailing data as well to ensure consistency between results.

Test Plan:
```
buck test koski/functions_contrib/df4ai/tests:box_cox_test -- SameInputSameOutput
buck2 test fbcode//caffe2/caffe2/python/operator_test:batch_box_cox_test
```

Rollback Plan:

Differential Revision: D82265247
@Yuhta
Copy link
Contributor Author

Yuhta commented Sep 12, 2025

@pytorchbot label "topic: not user facing"

@pytorch-bot pytorch-bot bot added the topic: not user facing topic category label Sep 12, 2025
Copy link
Contributor

@swolchok swolchok left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Review automatically exported from Phabricator review in Meta.

…ytorch#162772)

Summary:

The SIMD path is using SLEEF version of `pow` which is slightly different from `std::pow`.  The fix is to use the same vectorized code (with partial load and store) for the trailing data as well to ensure consistency between results.

Test Plan:
```
buck test koski/functions_contrib/df4ai/tests:box_cox_test -- SameInputSameOutput
buck2 test fbcode//caffe2/caffe2/python/operator_test:batch_box_cox_test
```

Rollback Plan:

Differential Revision: D82265247
@facebook-github-bot
Copy link
Contributor

@Yuhta has exported this pull request. If you are a Meta employee, you can view the originating diff in D82265247.

@Yuhta Yuhta changed the title [koski] Fix boxcox to return same result for same input in one batch Fix boxcox to return same result for same input in one batch Sep 12, 2025
@pytorch-bot pytorch-bot bot added the ciflow/trunk Trigger trunk jobs on your pull request label Sep 12, 2025
@facebook-github-bot
Copy link
Contributor

@pytorchbot merge

(Initiating merge automatically since Phabricator Diff has merged)

@pytorchmergebot
Copy link
Collaborator

Merge started

Your change will be merged once all checks pass (ETA 0-4 Hours).

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team

Advanced Debugging
Check the merge workflow status
here

markc-614 pushed a commit to markc-614/pytorch that referenced this pull request Sep 17, 2025
…#162772)

Summary:
The SIMD path is using SLEEF version of `pow` which is slightly different from `std::pow`.  The fix is to use the same vectorized code (with partial load and store) for the trailing data as well to ensure consistency between results.

Rollback Plan:

Differential Revision: D82265247

Pull Request resolved: pytorch#162772
Approved by: https://github.com/swolchok
@facebook-github-bot
Copy link
Contributor

@pytorchbot revert -m="Diff reverted internally" -c="ghfirst"

This Pull Request has been reverted by a revert inside Meta. To re-land this change, please open another pull request, assign the same reviewers, fix the CI failures that caused the revert and make sure that the failing CI runs on the PR by applying the proper ciflow label (e.g., ciflow/trunk).)

@pytorchmergebot
Copy link
Collaborator

@pytorchbot successfully started a revert job. Check the current status here.
Questions? Feedback? Please reach out to the PyTorch DevX Team

@pytorchmergebot
Copy link
Collaborator

@Yuhta your PR has been successfully reverted.

@facebook-github-bot
Copy link
Contributor

@pytorchbot merge -i

(Initiating merge automatically since Phabricator Diff has merged, merging with -i because oss signals were bypassed internally)

@pytorchmergebot
Copy link
Collaborator

Merge started

Your change will be merged while ignoring the following 0 checks:

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team

Advanced Debugging
Check the merge workflow status
here

@pytorchmergebot
Copy link
Collaborator

Merge failed

Reason: 1 jobs have failed, first few of them are: Meta Internal-Only Changes Check

Details for Dev Infra team Raised by workflow job

@wdvr
Copy link
Contributor

wdvr commented Sep 22, 2025

unlanded internally. @Yuhta please follow up on D82753931 and open a new PR if this needs to be relanded / re-exported

@wdvr wdvr closed this Sep 22, 2025
mansiag05 pushed a commit to mansiag05/pytorch that referenced this pull request Sep 22, 2025
…#162772)

Summary:
The SIMD path is using SLEEF version of `pow` which is slightly different from `std::pow`.  The fix is to use the same vectorized code (with partial load and store) for the trailing data as well to ensure consistency between results.

Rollback Plan:

Differential Revision: D82265247

Pull Request resolved: pytorch#162772
Approved by: https://github.com/swolchok
cleonard530 pushed a commit to cleonard530/pytorch that referenced this pull request Sep 22, 2025
…#162772)

Summary:
The SIMD path is using SLEEF version of `pow` which is slightly different from `std::pow`.  The fix is to use the same vectorized code (with partial load and store) for the trailing data as well to ensure consistency between results.

Rollback Plan:

Differential Revision: D82265247

Pull Request resolved: pytorch#162772
Approved by: https://github.com/swolchok
dsashidh pushed a commit to dsashidh/pytorch that referenced this pull request Sep 26, 2025
…#162772)

Summary:
The SIMD path is using SLEEF version of `pow` which is slightly different from `std::pow`.  The fix is to use the same vectorized code (with partial load and store) for the trailing data as well to ensure consistency between results.

Rollback Plan:

Differential Revision: D82265247

Pull Request resolved: pytorch#162772
Approved by: https://github.com/swolchok
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

caffe2 ci-no-td Do not run TD on this PR ciflow/trunk Trigger trunk jobs on your pull request fb-exported Merged meta-exported Reverted topic: not user facing topic category

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants