aboutsummaryrefslogtreecommitdiff
path: root/lldb/source/Plugins/ScriptInterpreter/Python/ScriptInterpreterPythonImpl.h
diff options
context:
space:
mode:
authorsrcarroll <50210727+srcarroll@users.noreply.github.com>2025-10-30 10:20:19 -0500
committerGitHub <noreply@github.com>2025-10-30 10:20:19 -0500
commitf5e175f06dacf6751f27f7a4bd9e9a3489e95a5e (patch)
tree61a2032ec85dd38101dda35f937bba6673a77c6b /lldb/source/Plugins/ScriptInterpreter/Python/ScriptInterpreterPythonImpl.h
parentba5cde79aa05eeaa87d45cf472f3583fa9f93bff (diff)
downloadllvm-f5e175f06dacf6751f27f7a4bd9e9a3489e95a5e.zip
llvm-f5e175f06dacf6751f27f7a4bd9e9a3489e95a5e.tar.gz
llvm-f5e175f06dacf6751f27f7a4bd9e9a3489e95a5e.tar.bz2
[mlir][linalg] Genericize MapOp (#162742)
This PR modifies the definition of `linalg::MapOp` so that it has the same structure of `linalg::GenericOp` and all other linalg ops. Mainly, it adds an `out` bbarg for the body of the op. Although the `out` arg is never used in the body, there doesn't seem to be much benefit in specializing the op to exclude it. In fact it only makes things more complicated because it doesn't align with the `GenericOp` structure. For example, `linalg-generalize-named-ops` avoided converting `linalg.map` purely because it didn't have the structure to do so. Moreover, although some fusion patterns are applied explicitly to `GenericOp`, we can change them to be applied to the base `LinalgOp` which will enable fusion for any fusion-compatible linalg op, but that requires the op having a generic structure. So these changes will enable us to use existing generic transformation patterns on `MapOp` that weren't possible before. They can either be applied to `MapOp` directly or applied after converting to `GenericOp`.
Diffstat (limited to 'lldb/source/Plugins/ScriptInterpreter/Python/ScriptInterpreterPythonImpl.h')
0 files changed, 0 insertions, 0 deletions