Fix triu and tril for zero-strided inputs on gpu #4962
Merged
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.
Fix #4840
This assumes that the output tensor for the operation (if you do inplace operation or if you used the
out=flag) does not have a zero-strided dimension.@apaszke iirc this is an assumption that we make all the time right? If so, do we want to explicitly enforce it at the python api level (one linear check of the stride compared to the python wrapping should be small)? Or do we want to say it explicitly in the documentation somewhere?