summaryrefslogtreecommitdiff
path: root/clang/lib/CodeGen/CodeGenModule.cpp
diff options
context:
space:
mode:
authorJames Newling <james.newling@gmail.com>2025-04-30 09:05:40 -0700
committerGitHub <noreply@github.com>2025-04-30 09:05:40 -0700
commitbad8bf56d3e4f107423b307f5f75564296703a76 (patch)
treeef27278550fffb1c23222f3bce5e3fc2fbfb9ad3 /clang/lib/CodeGen/CodeGenModule.cpp
parent0e9fb5202ce2c1e3cc43436dd4c4b8cd57fa1cef (diff)
[mlir][vector] Linearization: push 'bit width' logic out of patterns (#136581)
[NFC] Vector linearization is a collection of rewrite patterns that reduce the rank of vector operands and results. In https://github.com/llvm/llvm-project/pull/83314 an option to ignore (make 'legal') operations with large inner-most dimensions was added. This current PR is a step towards making that option live outside of upstream MLIR. The motivation is to remove non-core functionality (I would like to use this pass, but would prefer not to deal with 'targetVectorBitWidth` at all). As a follow-up to this PR, I propose that user(s) of the `targetVectorBitWidth` move the relevant code (now in mlir/test/lib/Dialect/Vector/TestVectorTransforms.cpp) to their code bases, and then eventually remove it from upstream. In addition the tests need to split out (I've intentionally not modified the lit tests here, to make it easier to confirm that this is a NFC). I'm happy to help make it easier to do this final step! The approach I've used is to move the logic pertaining to `targetVectorBitWidth` out the patterns, and into the conversion target, which the end user can control outside of core MLIR.
Diffstat (limited to 'clang/lib/CodeGen/CodeGenModule.cpp')
0 files changed, 0 insertions, 0 deletions