diff options
author | MaheshRavishankar <1663364+MaheshRavishankar@users.noreply.github.com> | 2025-06-10 12:13:42 -0700 |
---|---|---|
committer | GitHub <noreply@github.com> | 2025-06-10 12:13:42 -0700 |
commit | 45ae41e0d8e13c95d49cadf3abed44ddf1a0b741 (patch) | |
tree | d05e3126dfff851adb8a5d7114254aecc61657d0 /clang-tools-extra/clang-tidy/linuxkernel/LinuxKernelTidyModule.cpp | |
parent | 46b7a88548e5016f403cdc5f2cb1e4ff09353c3b (diff) | |
download | llvm-45ae41e0d8e13c95d49cadf3abed44ddf1a0b741.zip llvm-45ae41e0d8e13c95d49cadf3abed44ddf1a0b741.tar.gz llvm-45ae41e0d8e13c95d49cadf3abed44ddf1a0b741.tar.bz2 |
[mlir][scf] Return `replacements` explicitly in `SCFTilingResult`. (#143217)
In #120115 the replacements for the tiled operations were wrapped within
the `MergeResult` object. That is a bit of an obfuscation and not
immediately obvious where to get the replacements post tiling. This
changes the `SCFTilingResult` to have `replacements` explicit (as it was
before that change).
`mergeOps` is added as a separate field of `SCFTilingResult`, which is
empty when the reduction type is `FullReduction`.
This is a API breaking change. All uses of `mergeResult.replacements`
should be replaced with `replacements`.
There was also an implicit assumption that
`PartialReductionTilingInterface` is derived from `TilingInterface`, so
all ops that implemented the `PartialReductionTilingInterface` were
expected to implement the `TilingInterface` as well. This pre-dated the
existence of derived inheritances. Make
`PartialReductionTilingInterface` derive from `TilingInterface`.
Signed-off-by: MaheshRavishankar <mahesh.ravishankar@gmail.com>
Diffstat (limited to 'clang-tools-extra/clang-tidy/linuxkernel/LinuxKernelTidyModule.cpp')
0 files changed, 0 insertions, 0 deletions