| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
[mlir] add getViewDest method to viewLikeOpInterface (#154524) The viewLikeOpInterface abstracts the behavior of an operation view one buffer as another. However, the current interface only includes a "getViewSource" method and lacks a "getViewDest" method. Previously, it was generally assumed that viewLikeOpInterface operations would have only one return value, which was the view dest. This assumption was broken by memref.extract_strided_metadata, and more operations may break these silent conventions in the future. Calling "viewLikeInterface->getResult(0)" may lead to a core dump at runtime. Therefore, we need 'getViewDest' method to standardize our behavior. This patch adds the getViewDest function to viewLikeOpInterface and modifies the usage points of viewLikeOpInterface to standardize its use. | 11 个月前 | |
[MLIR][NFC] Retire let constructor for Bufferization (#129850) let constructor is legacy (do not use in tree!) since the table gen backend emits most of the glue logic to build a pass. | 1 年前 | |
[MLIR][BufferResultsToOutParamsPass] Add Option to Modify Public Function's Signature (#167248) Since https://github.com/llvm/llvm-project/pull/162441, buffer-results-to-out-params transforms private functions only. But, as mentioned in https://github.com/llvm/llvm-project/pull/162441#issuecomment-3404195242, this is a breaking change for pipelines handling C code. Our pipeline @EfficientComputer is also affected by this breaking change. Therefore, this PR adds an opt-in flag to allow public functions to be transformed by BufferResultsToOutParamsPass. | 8 个月前 | |
[mlir][NFC] update mlir/Dialect create APIs (15/n) (#149921) See https://github.com/llvm/llvm-project/pull/147168 for more info. | 1 年前 | |
[mlir] add getViewDest method to viewLikeOpInterface (#154524) The viewLikeOpInterface abstracts the behavior of an operation view one buffer as another. However, the current interface only includes a "getViewSource" method and lacks a "getViewDest" method. Previously, it was generally assumed that viewLikeOpInterface operations would have only one return value, which was the view dest. This assumption was broken by memref.extract_strided_metadata, and more operations may break these silent conventions in the future. Calling "viewLikeInterface->getResult(0)" may lead to a core dump at runtime. Therefore, we need 'getViewDest' method to standardize our behavior. This patch adds the getViewDest function to viewLikeOpInterface and modifies the usage points of viewLikeOpInterface to standardize its use. | 11 个月前 | |
[mlir][bufferization] Support custom types at function boundaries (#159766) Support custom types (3/N): allow custom tensor and buffer types in function signatures and at call-sites. This is one of the major building blocks to move in the direction of module-level one-shot-bufferization support. To achieve this, BufferizationOptions::FunctionArgTypeConverterFn callback is converted to work with tensor-like and buffer-like types, instead of the builtin counterparts. The default behavior for builtins remains unchanged, while custom types by default go through TensorLikeType::getBufferType() which is a general conversion interface. | 10 个月前 | |
[mlir][bufferization] Remove buffer-deallocation pass (#126366) The -buffer-deallocation pass is not compatible with One-Shot Bufferize and has been replaced with the Ownership-based Buffer Deallocation pass about 1.5 years ago. To clean up the code base, this commit removes the deprecated buffer-deallocation pass. All uses of this deprecated pass within MLIR have already been migrated. Note for LLVM integration: If you depend on this pass, migrate to the Ownership-based Buffer Deallocation pass or copy the pass to your codebase. For details, see https://discourse.llvm.org/t/psa-bufferization-new-buffer-deallocation-pipeline/73375. | 1 年前 | |
[mlir][bufferize] Make drop-equivalent-buffer-results support mult blocks (#163388) Enable Make drop-equivalent-buffer-results to handle return ops in multiple blocks within a function. | 9 个月前 | |
[mlir][NFC] update mlir/Dialect create APIs (15/n) (#149921) See https://github.com/llvm/llvm-project/pull/147168 for more info. | 1 年前 | |
[mlir] Remove unused includes (NFC) (#147549) These are identified by misc-include-cleaner. I've filtered out those that break builds. Also, I'm staying away from llvm-config.h, config.h, and Compiler.h, which likely cause platform- or compiler-specific build failures. | 1 年前 | |
[mlir][bufferize] Use resolveCallableInTable to cleanup getCalledFunction (NFC) (#165658) Simplify the implementation of getCalledFunction using resolveCallableInTable. | 9 个月前 | |
[mlir][NFC] update mlir/Dialect create APIs (33/n) (#150659) See https://github.com/llvm/llvm-project/pull/147168 for more info. | 1 年前 | |
[mlir] Remove a redundant cast (NFC) (#168241) llvm::all_of already returns bool. Identified with readability-redundant-casting. | 8 个月前 | |
[mlir][bufferize] Use resolveCallableInTable to cleanup getCalledFunction (NFC) (#165658) Simplify the implementation of getCalledFunction using resolveCallableInTable. | 9 个月前 | |
[MLIR] Apply clang-tidy fixes for llvm-qualified-auto in OptimizeAllocationLiveness.cpp (NFC) | 11 个月前 | |
[MLIR] Revamp RegionBranchOpInterface (#165429) This is still somehow a WIP, we have some issues with this interface that are not trivial to solve. This patch tries to make the concepts of RegionBranchPoint and RegionSuccessor more robust and aligned with their definition: - A RegionBranchPoint is either the parent (RegionBranchOpInterface) op or a RegionBranchTerminatorOpInterface operation in a nested region. - A RegionSuccessor is either one of the nested region or the parent RegionBranchOpInterface Some new methods with reasonnable default implementation are added to help resolving the flow of values across the RegionBranchOpInterface. It is still not trivial in the current state to walk the def-use chain backward with this interface. For example when you have the 3rd block argument in the entry block of a for-loop, finding the matching operands requires to know about the hidden loop iterator block argument and where the iterargs start. The API is designed around forward-tracking of the chain unfortunately. Try to reland #161575 ; I suspect a buildbot incremental build issue. | 9 个月前 | |
[mlir][bufferize] Cleanup TensorCopyInsertion.cpp (NFC) (#164541) | 9 个月前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 11 个月前 | ||
| 1 年前 | ||
| 8 个月前 | ||
| 1 年前 | ||
| 11 个月前 | ||
| 10 个月前 | ||
| 1 年前 | ||
| 9 个月前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 9 个月前 | ||
| 1 年前 | ||
| 8 个月前 | ||
| 9 个月前 | ||
| 11 个月前 | ||
| 9 个月前 | ||
| 9 个月前 |