-
Notifications
You must be signed in to change notification settings - Fork 26.3k
Delete deprecated fp32 precision warnings (#166956) #166998
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/166998
Note: Links to docs will display an error until the docs builds have been completed. ❗ 1 Active SEVsThere are 1 currently active SEVs. If your PR is affected, please view them below: ✅ No FailuresAs of commit f904e71 with merge base 4840a1a ( This comment was automatically generated by Dr. CI and updates every 15 minutes. |
|
cc @zou3519 @BoyuanFeng to validate this manual cherrypick looks correct |
| #endif | ||
| namespace at { | ||
|
|
||
| namespace { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
er don't you still need the anonymous namespace?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep patching that on my end
The deprecation warning led to warning spamming in PyTorch APIs, like torch.compile. This is not how a deprecation warning should go: if we add a deprecation warning, we'd better update our built-in APIs to prevent warning spam. Pull Request resolved: #166956 Approved by: https://github.com/albanD (cherry picked from commit 527b110)
e860e2f to
f904e71
Compare
zou3519
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm as long as it compiles
The deprecation warning led to warning spamming in PyTorch APIs, like torch.compile. This is not how a deprecation warning should go: if we add a deprecation warning, we'd better update our built-in APIs to prevent warning spam.
Pull Request resolved: #166956 Approved by: https://github.com/albanD
(cherry picked from commit 527b110)
Fixes #166286