[Mlir-commits] [mlir] [mlir] Fix semantics of linalg::ReduceOp with several inputs (PR #107005)
llvmlistbot at llvm.org
llvmlistbot at llvm.org
Fri Nov 1 17:10:39 PDT 2024
================
@@ -485,6 +485,48 @@ func.func @variadic_reduce_memref(%input1: memref<16x32x64xf32>,
// -----
+func.func @reduce_asymmetric(%input: tensor<16x32x64xi32>, %input2: tensor<16x32x64xi32>,
+ %init: tensor<16x64xi32>) -> tensor<16x64xi32> {
+ %reduce = linalg.reduce
----------------
MaheshRavishankar wrote:
Like I dont understand what this is trying to do. You are effectively doing a multiply and a reduce? How is this different from just using a `linalg.generic`. As in why use a `linalg.reduce` better than `linalg.generic`?
https://github.com/llvm/llvm-project/pull/107005
More information about the Mlir-commits
mailing list