[Mlir-commits] [mlir] [MLIR][XeGPU] Remove the transpose attribte from Gather/Scatter ops and Cleanup the documents (PR #145389)
Charitha Saumya
llvmlistbot at llvm.org
Tue Jun 24 10:00:53 PDT 2025
================
@@ -609,19 +572,13 @@ def XeGPU_LoadGatherOp : XeGPU_Op<"load", [
let description = [{ It (aka. load) load data per each work-item. The output
describes the data being loaded at the subgroup level, so its size is
consistent with the number of work-items in a subgroup. When the chunk size
- is larger than 2, the output vector is a 2D vector, with dim-1 correspoding
- to work-items, and dim-0 corresponding to the chunk size loaded by each work-item.
- Specially, there is a transpose effect on the result (as compared to the TensorDesc)
- due to the hardware implementation. Therefore, a transpose attribute is introduced
- on purpose, making sure users are aware of this implicit transformation.
-
+ is larger than 2, the output vector is a 2D vector, with dim-0 correspoding
+ to work-items, and dim-1 corresponding to the chunk size loaded by each work-item.
----------------
charithaintc wrote:
Are we assuming here that there will always be a transpose operation after the load?
I wonder how a user can understand the semantics of this op. what if the user does not want the transpose and want to use the op in isolation (which is perfectly legal)?
https://github.com/llvm/llvm-project/pull/145389
More information about the Mlir-commits
mailing list