| commit | 45ae41e0d8e13c95d49cadf3abed44ddf1a0b741 | [log] [tgz] |
|---|---|---|
| author | MaheshRavishankar <1663364+MaheshRavishankar@users.noreply.github.com> | Tue Jun 10 12:13:42 2025 -0700 |
| committer | GitHub <noreply@github.com> | Tue Jun 10 12:13:42 2025 -0700 |
| tree | d05e3126dfff851adb8a5d7114254aecc61657d0 | |
| parent | 46b7a88548e5016f403cdc5f2cb1e4ff09353c3b [diff] |
[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>
Welcome to the LLVM project!
This repository contains the source code for LLVM, a toolkit for the construction of highly optimized compilers, optimizers, and run-time environments.
The LLVM project has multiple components. The core of the project is itself called “LLVM”. This contains all of the tools, libraries, and header files needed to process intermediate representations and convert them into object files. Tools include an assembler, disassembler, bitcode analyzer, and bitcode optimizer.
C-like languages use the Clang frontend. This component compiles C, C++, Objective-C, and Objective-C++ code into LLVM bitcode -- and from there into object files, using LLVM.
Other components include: the libc++ C++ standard library, the LLD linker, and more.
Consult the Getting Started with LLVM page for information on building and running LLVM.
For information on how to contribute to the LLVM project, please take a look at the Contributing to LLVM guide.
Join the LLVM Discourse forums, Discord chat, LLVM Office Hours or Regular sync-ups.
The LLVM project has adopted a code of conduct for participants to all modes of communication within the project.