-
Notifications
You must be signed in to change notification settings - Fork 61
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
Fixed the bug to access tensor stride #150
Conversation
This pull request was exported from Phabricator. Differential Revision: D60642585 |
This pull request was exported from Phabricator. Differential Revision: D60642585 |
f99d5ed
to
efc853d
Compare
Summary: Pull Request resolved: facebookresearch#150 There is a bug to access tensor stride. The current implementation uses the index of the input tensor to access node.tensor_strides. However node.tensor_strides is for all input variables including non tensor variables. So the fix is to get the list of tensor stride, then uses the index of the input tensor to access the list of tensor stride. Differential Revision: D60642585
This pull request was exported from Phabricator. Differential Revision: D60642585 |
Summary: Pull Request resolved: facebookresearch#150 There is a bug to access tensor stride. The current implementation uses the index of the input tensor to access node.tensor_strides. However node.tensor_strides is for all input variables including non tensor variables. So the fix is to get the list of tensor stride, then uses the index of the input tensor to access the list of tensor stride. Differential Revision: D60642585
efc853d
to
07331b4
Compare
This pull request was exported from Phabricator. Differential Revision: D60642585 |
Summary: Pull Request resolved: facebookresearch#150 There is a bug to access tensor stride. The current implementation uses the index of the input tensor to access node.tensor_strides. However node.tensor_strides is for all input variables including non tensor variables. So the fix is to get the list of tensor stride, then uses the index of the input tensor to access the list of tensor stride. Differential Revision: D60642585
07331b4
to
431b634
Compare
Summary: Pull Request resolved: facebookresearch#150 There is a bug to access tensor stride. The current implementation uses the index of the input tensor to access node.tensor_strides. However node.tensor_strides is for all input variables including non tensor variables. So the fix is to get the list of tensor stride, then uses the index of the input tensor to access the list of tensor stride. Reviewed By: briancoutinho Differential Revision: D60642585
This pull request was exported from Phabricator. Differential Revision: D60642585 |
431b634
to
78036a4
Compare
This pull request has been merged in 58ce6eb. |
Summary: There is a bug to access tensor stride. The current implementation uses the index of the input tensor to access node.tensor_strides. However node.tensor_strides is for all input variables including non tensor variables. So the fix is to get the list of tensor stride, then uses the index of the input tensor to access the list of tensor stride.
Differential Revision: D60642585