[Mlir-commits] [mlir] [mlir][linalg] Convert linalg.named to linalg.elementwise op. (PR #148424)
Javed Absar
llvmlistbot at llvm.org
Mon Jul 14 02:36:58 PDT 2025
javedabsar1 wrote:
> users can pick-and-choose separately which stage they stop for each step of the way.
Thanks @rengolin -- good thinking on extending this concept/PR.
We need conversion from existing named to new ops in the tree (https://discourse.llvm.org/t/rfc-mlir-linalg-operation-tree/83586) otherwise we don't have that many use case for new ops .
1. named -->generic : already exists ( `mlir-opt --linalg-generalize-named-ops` ).
2. named --> linalg.element_wise , linalg.contraction : This PR `mlir-opt -linalg-named-to-elementwise`. We can rename it to cover contraction-op etc.
3. elementwise/contraction --> named : Do we want this? I dont see a use case at least to me.
4. generic to named : -linalg-specialize-generic-ops I did some work on this previously as you know but in general this path is not always possible (fused, handwritten generic).
5. generic to elementwise/contract - I think this falls to specialize.
We could discuss further in next Lighthouse meeting? Meanwhile, some common agreement -- e.g.
https://github.com/llvm/llvm-project/pull/148424
More information about the Mlir-commits
mailing list