aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/Bitcode
diff options
context:
space:
mode:
authorfabrizio-indirli <fabrizio.indirli@arm.com>2025-07-22 10:16:59 +0100
committerGitHub <noreply@github.com>2025-07-22 10:16:59 +0100
commit3e7433d75a0c03a84e6b1c8e5e5eda347d72a8ff (patch)
tree80591c48910c3edba2152a770dbf516049d25d66 /llvm/lib/Bitcode
parent73b85f87e4771d04e02912a8c2f39ab67910a04d (diff)
downloadllvm-3e7433d75a0c03a84e6b1c8e5e5eda347d72a8ff.zip
llvm-3e7433d75a0c03a84e6b1c8e5e5eda347d72a8ff.tar.gz
llvm-3e7433d75a0c03a84e6b1c8e5e5eda347d72a8ff.tar.bz2
[mlir][linalg] Fix to Elementwise Fusion when preserving results (#149843)
In the linalg ElementwiseOpFusion transform, a pre-requisite for the fusion between a producer and consumer op is that the producer's output indexing map associated to the result to be fused must be invertible (e.g. a simple permutation). Before this patch, only the first output indexing map was being checked; this bug produced issues when the operand to fuse was not the 1st result of the producer op. For example, this situation arises when the producer op has multiple results because it's the result of previous fusions where the original result had been preserved: in these cases, the pass ought to check the indexing map of the result being fused, which is not necessarily the 1st one. Signed-off-by: Fabrizio Indirli <Fabrizio.Indirli@arm.com>
Diffstat (limited to 'llvm/lib/Bitcode')
0 files changed, 0 insertions, 0 deletions