-
Notifications
You must be signed in to change notification settings - Fork 607
Enable zero-size tensors #3640
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
Enable zero-size tensors #3640
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/3640
Note: Links to docs will display an error until the docs builds have been completed. ❌ 1 New FailureAs of commit b49c28d with merge base 46ec26b ( NEW FAILURE - The following job has failed:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
This pull request was exported from Phabricator. Differential Revision: D57450473 |
Summary: As title. The approach is slightly different than in PyTorch Vulkan. Instead of binding no memory, we make a small allocation. The reason for this change is to account for the possibility that some zero size tensors are used as input but the output is not zero size. In that case we still need to be able to bind the zero size tensor to a shader. Differential Revision: D57450473
This pull request was exported from Phabricator. Differential Revision: D57450473 |
Summary: As title. The approach is slightly different than in PyTorch Vulkan. Instead of binding no memory, we make a small allocation. The reason for this change is to account for the possibility that some zero size tensors are used as input but the output is not zero size. In that case we still need to be able to bind the zero size tensor to a shader. Reviewed By: yipjustin Differential Revision: D57450473
This pull request was exported from Phabricator. Differential Revision: D57450473 |
Summary: As title. The approach is slightly different than in PyTorch Vulkan. Instead of binding no memory, we make a small allocation. The reason for this change is to account for the possibility that some zero size tensors are used as input but the output is not zero size. In that case we still need to be able to bind the zero size tensor to a shader. Reviewed By: yipjustin Differential Revision: D57450473
This pull request was exported from Phabricator. Differential Revision: D57450473 |
This pull request has been merged in 5c70121. |
Summary: `batch_norm` has been implemented in [PR 3569](pytorch#3569), but not registered due to 0-size tensors were not supported then. Since 0-size tensors are supported in [PR 3640](pytorch#3640), we can register this op now. Differential Revision: D57707822
Summary: Pull Request resolved: #3716 `batch_norm` has been implemented in [PR 3569](#3569), but not registered due to 0-size tensors were not supported then. Since 0-size tensors are supported in [PR 3640](#3640), we can register this op now. Reviewed By: jorgep31415 Differential Revision: D57707822 fbshipit-source-id: ec293adc29a4d16ea56d6cd7bba7a3b7fa4c7d6e
Summary: Pull Request resolved: pytorch#3716 `batch_norm` has been implemented in [PR 3569](pytorch#3569), but not registered due to 0-size tensors were not supported then. Since 0-size tensors are supported in [PR 3640](pytorch#3640), we can register this op now. Reviewed By: jorgep31415 Differential Revision: D57707822 fbshipit-source-id: ec293adc29a4d16ea56d6cd7bba7a3b7fa4c7d6e
Summary:
As title.
The approach is slightly different than in PyTorch Vulkan. Instead of binding no memory, we make a small allocation. The reason for this change is to account for the possibility that some zero size tensors are used as input but the output is not zero size. In that case we still need to be able to bind the zero size tensor to a shader.
Differential Revision: D57450473