[release/1.10.0] Fix non-contiguous inputs in fused RoPE (#334)#336
Merged
pragupta merged 1 commit intoJul 1, 2026
Merged
Conversation
pragupta
approved these changes
Jul 1, 2026
pragupta
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Cherry-pick of #334 (commit 77b96da) into
release/1.10.0.The aiter fused RoPE kernels require the head-dim (last) stride to be 1. This enforces contiguity on non-contiguous inputs/gradients in the forward and backward paths of
FusedRoPEFuncAiter,FusedRoPECachedFuncAiter,FusedRoPETHDFuncAiter, andFusedRoPE2DFuncAiter.The
FusedRoPE2DFuncAiterhunks required a trivial conflict resolution (trailing-whitespace-only blank lines on this branch); the net change is identical to the original commit.