Fix fbgemm::permute_1D_sparse_data's aliasing behavior #2180
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary:
The schema for this operator promises that it is functional (that is, it does
not return output Tensors that are views on the inputs). There is a fast-path
that does return views on the input. We change it to return clones instead of
views. fbgemm::permute_2d_sparse_data already has this fix; looks like we just
didn't apply it to fbgemm::permute_1d_sparse_data
Differential Revision: D51711257