-
Notifications
You must be signed in to change notification settings - Fork 25.5k
Remove some Half support in some binary CPU kernels #33021
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
💊 CircleCI build failures summary and remediationsAs of commit 59e5908: Commit 59e5908 was recently pushed. Waiting for builds... This comment was automatically generated by Dr. CI (expand for details).Follow this link to opt-out of these comments for your Pull Requests.Please report bugs/suggestions on the GitHub issue tracker. This comment has been revised 2 times. |
so, this was already released in 1.4.0. I don't think the backwards ones matter because you can't invoke them anyway (we can remove them if we want), but probably not worth doing for mse. |
f8fd2ac
to
99c044c
Compare
@gchanan OK, I added a warning to the MSE kernel. |
They were probably mistakenly added as we do not intend to support Half on CPUs in general and in these situations Half type would probably be significantly slower than their float and double counterpart due to the lack of vectorization and the need of additional casting.
99c044c
to
59e5908
Compare
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.
@VitalyFedyunin has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator.
@VitalyFedyunin merged this pull request in 45818a3. |
…ions on CPU For reasons similar to pytorch#33021. Note that the support of half type has not been available in any releases yet.
…ions on CPU (#33206) Summary: For reasons similar to #33021. Note that the support of half type has not been available in any releases yet so it should be safe to remove (All forward ones concerning this PR were added in daef363 and 8cb05e7) Pull Request resolved: #33206 Differential Revision: D19861137 Pulled By: ezyang fbshipit-source-id: 38a3a398a716a782c26a611c56ddeab7eb7ac79e
Summary: They were probably mistakenly added as we do not intend to support Half on CPUs in general and in these situations Half type would probably be significantly slower than their float and double counterpart due to the lack of vectorization and the need of additional casting. cc XiaobingSuper Pull Request resolved: pytorch#33021 Differential Revision: D19795152 Pulled By: VitalyFedyunin fbshipit-source-id: b19796db88880a46557e1b2fd06e584d46093562
…ions on CPU (pytorch#33206) Summary: For reasons similar to pytorch#33021. Note that the support of half type has not been available in any releases yet so it should be safe to remove (All forward ones concerning this PR were added in daef363 and 8cb05e7) Pull Request resolved: pytorch#33206 Differential Revision: D19861137 Pulled By: ezyang fbshipit-source-id: 38a3a398a716a782c26a611c56ddeab7eb7ac79e
@VitalyFedyunin @gchanan This isn't BC-breaking, right? sigmoid_backward_kernel and tanh_backward_kernel can't be accessed directly and we added a warning for MSELoss |
Confirmed with @VitalyFedyunin offline that this is not BC breaking |
Was added by #33021, but modern CPUs right now are quite capable of handling half precision types. Alternatively one can guard the warning with `#ifdef x86_64` Pull Request resolved: #139961 Approved by: https://github.com/jgong5
Was added by pytorch#33021, but modern CPUs right now are quite capable of handling half precision types. Alternatively one can guard the warning with `#ifdef x86_64` Pull Request resolved: pytorch#139961 Approved by: https://github.com/jgong5
Was added by pytorch#33021, but modern CPUs right now are quite capable of handling half precision types. Alternatively one can guard the warning with `#ifdef x86_64` Pull Request resolved: pytorch#139961 Approved by: https://github.com/jgong5
Was added by pytorch#33021, but modern CPUs right now are quite capable of handling half precision types. Alternatively one can guard the warning with `#ifdef x86_64` Pull Request resolved: pytorch#139961 Approved by: https://github.com/jgong5
Was added by pytorch#33021, but modern CPUs right now are quite capable of handling half precision types. Alternatively one can guard the warning with `#ifdef x86_64` Pull Request resolved: pytorch#139961 Approved by: https://github.com/jgong5
Was added by pytorch#33021, but modern CPUs right now are quite capable of handling half precision types. Alternatively one can guard the warning with `#ifdef x86_64` Pull Request resolved: pytorch#139961 Approved by: https://github.com/jgong5
They were probably mistakenly added as we do not intend to support Half
on CPUs in general and in these situations Half type would probably be
significantly slower than their float and double counterpart due to the
lack of vectorization and the need of additional casting.
cc @XiaobingSuper