Skip to content

[WIP] Unified G_BUILD_VECTOR combine #385

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

Draft
wants to merge 2 commits into
base: aie-public
Choose a base branch
from

Conversation

abhinay-anubola
Copy link
Collaborator

No description provided.

@abhinay-anubola abhinay-anubola changed the title [WIP] Unified G_BUILD_VECTOR_COMBINE [WIP] Unified G_BUILD_VECTOR combine Mar 12, 2025
if (!DifferingReg.isValid() || !SplatReg.isValid())
case 2:
// Check for single differing lane splat, as there are 2 unique registers.
return matchSingleDiffSplatVector(UniqueRegs, DstVecReg, MRI, MatchInfo);
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd like to take this further. We still have separate apply lambdas. Instead, we could match a splat pattern, and pack enough information in the apply lambda so that it can build the broadcast of the splat, and then, if we have different elements, perform one (or more) additional inserts. I'd make the apply lambda accept any number of additional asserts, and let the match function decide how many to allow.
The next step is then to recognize that the generic build vector inserts all elements on top of an undefined, so that we can also reuse that apply lambda to build a generic vector. Note that a broadcast is no more expensive than an insert into an undef.. The inserts could also be done by push lo or push hi.

Copy link
Collaborator

@martien-de-jong martien-de-jong Mar 13, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's more fun to be had, by imagining the different registers to be inserted in vectors, and translating the BUILD initializer to a shufflemask. By virtualizing the shuffle match and apply methods, you could then build on all of the shuffle tricks, e.g. to create two (or more) broadcast vectors for two different registers, and to pick from the two using a a (or more) VSELs. (Not now, just to illustrate reuse possibilities)

@khallouh
Copy link
Collaborator

Could you handle the case when some are undefs? See the following pattern from Reduce where %55 is undef so we should be able to broadcast %17 and insert %52 as a diff element:
%53:_(<64 x s8>) = G_BUILD_VECTOR %52(s8), %17(s8), %17(s8), %17(s8), %17(s8), %17(s8), %17(s8), %17(s8), %17(s8), %17(s8), %17(s8), %17(s8), %17(s8), %17(s8), %17(s8), %17(s8), %17(s8), %17(s8), %17(s8), %17(s8), %17(s8), %17(s8), %17(s8), %17(s8), %17(s8), %17(s8), %17(s8), %17(s8), %17(s8), %17(s8), %17(s8), %17(s8), %55(s8), %55(s8), %55(s8), %55(s8), %55(s8), %55(s8), %55(s8), %55(s8), %55(s8), %55(s8), %55(s8), %55(s8), %55(s8), %55(s8), %55(s8), %55(s8), %55(s8), %55(s8), %55(s8), %55(s8), %55(s8), %55(s8), %55(s8), %55(s8), %55(s8), %55(s8), %55(s8), %55(s8), %55(s8)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants