Adapt the rewriteAsPaddedOp method to use the OpBuilder instead of the PatterRewriter.
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
mlir/lib/Dialect/Linalg/Transforms/Transforms.cpp | ||
---|---|---|
164 | this older exit condition seems fishy, can this be cleaned up ? |
mlir/lib/Dialect/Linalg/Transforms/Transforms.cpp | ||
---|---|---|
164 | If paddingFunc returns failure we do not have a padding value. I agree the clean solution should be return failure in that case. But the exit condition will stay there. I will clean this up. |
mlir/lib/Dialect/Linalg/Transforms/Transforms.cpp | ||
---|---|---|
164 | Turns out it is still needed. We use paddingFunc also to control if a specific operand shall be padded. So if there is no padding value this is actually not a failure but a success. We can refactor this once we use all the new flags / padding control. |
this older exit condition seems fishy, can this be cleaned up ?