[CK_TILE] Non-K Major from old CK to CK-Tile - fix reverted PR#3199
Merged
Conversation
aosewski
approved these changes
Nov 17, 2025
AviralGoelAMD
pushed a commit
that referenced
this pull request
Nov 28, 2025
* Reapply "[CK_TILE] Non-K Major from old CK to CK-Tile (#2442)" (#3017) This reverts commit e4298e5. * WIP * take Y2 as the AK1/BK1 value, that is the 'vector size' after shuffle * use get_n_lds_banks() * clang-format --------- Co-authored-by: Adam Osewski <19374865+aosewski@users.noreply.github.com>
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
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.
Proposed changes
Unrevert previous revert #3017 of #2442
Checklist
Please put an
xinto the boxes that apply. You can also fill these out after creating the PR. If you're not sure, please don't hesitate to ask.clang-formaton all changed filesDiscussion
If this is a relatively large or complex change, feel free to start a discussion by explaining why you chose the solution you did and what alternatives you considered