-
Notifications
You must be signed in to change notification settings - Fork 13.5k
[mlir][ArmSME] Add mask operand to store_tile_slice #70838
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
[mlir][ArmSME] Add mask operand to store_tile_slice #70838
Conversation
240c712
to
26bb905
Compare
$tile `,` $tile_slice_index `,` $base `[` $indices `]` (`layout` `` $layout^)? | ||
attr-dict `:` type($base) `,` type($tile) | ||
$tile `,` $tile_slice_index `,` $mask `,` $base `[` $indices `]` (`layout` `` $layout^)? | ||
attr-dict `:` type($base) `,` type($mask) `,` type($tile) |
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.
Is this type($mask)
needed? It should be inferred from your TileSliceMaskConstraint
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.
No it can be inferred as you say, but I decided to add the type anyway since this maps 1-1 with intrinsic. tile_load
/tile_store
are aligned with Vector transfer read/write so I didn't add mask type to asm for those.
The type is also present in load_tile_slice
, we could remove in a follow-up if desired? I've don't mind either way.
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.
I prefer omitting the types that are very clear from context (i.e. the mask size must match the slice), but this is fine for now.
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.
Ok cool cheers, I'll post a follow-up :)
No description provided.