aboutsummaryrefslogtreecommitdiff
path: root/lldb/packages/Python/lldbsuite/test/gdbclientutils.py
diff options
context:
space:
mode:
authorMaheshRavishankar <1663364+MaheshRavishankar@users.noreply.github.com>2024-09-11 22:15:43 -0700
committerGitHub <noreply@github.com>2024-09-11 22:15:43 -0700
commitd5f0969c96224a44062715751da3c369ce5ea3f8 (patch)
treec3cfa3ba2430c4a8862b67a0c6819af7f433a898 /lldb/packages/Python/lldbsuite/test/gdbclientutils.py
parent1211d97922d62470ac8bc658f7bfe57e8b46a107 (diff)
downloadllvm-d5f0969c96224a44062715751da3c369ce5ea3f8.zip
llvm-d5f0969c96224a44062715751da3c369ce5ea3f8.tar.gz
llvm-d5f0969c96224a44062715751da3c369ce5ea3f8.tar.bz2
[mlir][TilingInterface] Avoid looking at operands for getting slices to continue tile + fuse. (#107882)
Current implementation of `scf::tileConsumerAndFuseProducerUsingSCF` looks at operands of tiled/tiled+fused operations to see if they are produced by `extract_slice` operations to populate the worklist used to continue fusion. This implicit assumption does not always work. Instead make the implementations of `getTiledImplementation` return the slices to use to continue fusion. This is a breaking change - To continue to get the same behavior of `scf::tileConsumerAndFuseProducerUsingSCF`, change all out-of-tree implementation of `TilingInterface::getTiledImplementation` to return the slices to continue fusion on. All in-tree implementations have been adapted to this. - This change touches parts that required a simplification to the `ControlFn` in `scf::SCFTileAndFuseOptions`. It now returns a `std::optional<scf::SCFTileAndFuseOptions::ControlFnResult>` object that should be `std::nullopt` if fusion is not to be performed. Signed-off-by: MaheshRavishankar <mahesh.revishankar@gmail.com>
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/gdbclientutils.py')
0 files changed, 0 insertions, 0 deletions