aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/Support/ProgramStack.cpp
diff options
context:
space:
mode:
authorAndrzej Warzyński <andrzej.warzynski@arm.com>2025-04-15 16:58:35 +0200
committerGitHub <noreply@github.com>2025-04-15 16:58:35 +0200
commitf215a61891b0368d2d7e329bc994c9053dc3fac9 (patch)
treee7d22a01bdbf140b673a8093851953201120d468 /llvm/lib/Support/ProgramStack.cpp
parent478065882303823623e1bc2d62b2a98097f9f53d (diff)
downloadllvm-f215a61891b0368d2d7e329bc994c9053dc3fac9.zip
llvm-f215a61891b0368d2d7e329bc994c9053dc3fac9.tar.gz
llvm-f215a61891b0368d2d7e329bc994c9053dc3fac9.tar.bz2
[mlir][linalg][vector] Refine create{Read|Write}OrMasked{Read|Write} (nfc) (#135350)
The semantics of `createReadOrMaskedRead` and `createWriteOrMaskedWrite` are currently a bit inconsistent and not fully documented: * The input vector sizes are passed as `readShape` and `inputVectorSizes`, respectively — inconsistent naming. * Currently, the input vector sizes in `createWriteOrMaskedWrite` are not required to be complete: any missing trailing sizes are inferred from the destination tensor. This only works when the destination tensor is statically shaped. * Unlike `createReadOrMaskedRead`, the documentation for `createWriteOrMaskedWrite` does not specify that write offsets are hard-coded to 0. This PR only updates the documentation and unifies the naming. As such, it is NFC. A follow-up PR will generalize and unify the implementation to support, for example, dynamically shaped destination tensors — a requirement for enabling scalable vectorization of `linalg.pack` and `linalg.unpack`.
Diffstat (limited to 'llvm/lib/Support/ProgramStack.cpp')
0 files changed, 0 insertions, 0 deletions