-
Notifications
You must be signed in to change notification settings - Fork 25
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
[TKW] Optimize trivial gather offsets #291
Conversation
@harsh-nod here is the patch to get rid of trivial gathers |
Thanks |
704c227
to
d2e506a
Compare
Signed-off-by: Ivan Butygin <[email protected]>
Signed-off-by: Ivan Butygin <[email protected]>
d2e506a
to
71c0564
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we not have tests to showcase this?
Yeah, it's kind of hard to construct artificial example for it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall change LGTM, did you try locally cherry-picking on top of Harsh's usecase/commit to see if it get rids of the issue he has? If yes, I think we can merge it. :)
Update gather/scatter offset generation to handle trivial contiguous offsets (i.e. `[0,1,2,3]`) and generate contiguous load/store instead. --------- Signed-off-by: Ivan Butygin <[email protected]>
Signed-off-by: Ivan Butygin <[email protected]>
Update gather/scatter offset generation to handle trivial contiguous offsets (i.e.
[0,1,2,3]
) and generate contiguous load/store instead.