-
Notifications
You must be signed in to change notification settings - Fork 751
Check overflow in allocation #12683
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
Check overflow in allocation #12683
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/12683
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit 9ba1c99 with merge base b183830 ( This comment was automatically generated by Dr. CI and updates every 15 minutes. |
|
This pull request was exported from Phabricator. Differential Revision: D78678540 |
This PR needs a
|
Summary: Overflow is unsafe as a user will get back much less memory then expected Differential Revision: D78678540
d43968a to
a4fb7f1
Compare
lucylq
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.
linter?
Summary: Overflow is unsafe as a user will get back much less memory then expected Reviewed By: lucylq Differential Revision: D78678540
a4fb7f1 to
2eb0e87
Compare
|
This pull request was exported from Phabricator. Differential Revision: D78678540 |
Summary: Overflow is unsafe as a user will get back much less memory then expected Reviewed By: lucylq Differential Revision: D78678540
2eb0e87 to
9ba1c99
Compare
|
This pull request was exported from Phabricator. Differential Revision: D78678540 |
Differential Revision: D78678540 Pull Request resolved: pytorch#12683
Summary: Overflow is unsafe as a user will get back much less memory then expected
Differential Revision: D78678540