[MLIR][XeGPU] Honor convert_layout's input_layout when resolving layout conflict#194935
Draft
[MLIR][XeGPU] Honor convert_layout's input_layout when resolving layout conflict#194935
Conversation
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
1 participant
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.
This PR changes getConsumerLayoutAt now to return the input_layout attribute directly when the consuming op is xegpu.convert_layout, since its required operand layout is explicitly declared rather than inferable from the result. This lets ResolveLayoutConflicts detect a real mismatch against the producer's layout and insert a bridging convert_layout, instead of being masked by the fallback that returned the producer's own layout.