en Copyright 2015 Java http://172.16.0.5:8080/history/llvm-project-15.0.7/mlir/test/Integration/Dialect/SparseTensor/CPU/sparse_sum.mlir#27a431f5 [mlir][bufferization][NFC] Move sparse_tensor.release to bufferization dialectThis op used to belong to the sparse dialect, but there are use cases for dense bufferization as well. (E.g., when a tensor alloc is returned from a function and should be deallocated at the call site.) This change moves the op to the bufferization dialect, which now has an `alloc_tensor` and a `dealloc_tensor` op.Differential Revision: https://reviews.llvm.org/D129985 List of files: /llvm-project-15.0.7/mlir/test/Integration/Dialect/SparseTensor/CPU/sparse_sum.mlir Tue, 19 Jul 2022 07:13:53 +0000 Matthias Springer <springerm@google.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/mlir/test/Integration/Dialect/SparseTensor/CPU/sparse_sum.mlir#c66303c2 [mlir][sparse] Switch to One-Shot BufferizeThis change removes the partial bufferization passes from the sparse compilation pipeline and replaces them with One-Shot Bufferize. One-Shot Analysis (and TensorCopyInsertion) is used to resolve all out-of-place bufferizations, dense and sparse. Dense ops are then bufferized with BufferizableOpInterface. Sparse ops are still bufferized in the Sparsification pass.Details:* Dense allocations are automatically deallocated, unless they are yielded from a block. (In that case the alloc would leak.) All test cases are modified accordingly. E.g., some funcs now have an "out" tensor argument that is returned from the function. (That way, the allocation happens at the call site.)* Sparse allocations are *not* automatically deallocated. They must be "released" manually. (No change, this will be addressed in a future change.)* Sparse tensor copies are not supported yet. (Future change)* Sparsification no longer has to consider inplacability. If necessary, allocations and/or copies are inserted during TensorCopyInsertion. All tensors are inplaceable by the time Sparsification is running. Instead of marking a tensor as "not inplaceable", it can be marked as "not writable", which will trigger an allocation and/or copy during TensorCopyInsertion.Differential Revision: https://reviews.llvm.org/D129356 List of files: /llvm-project-15.0.7/mlir/test/Integration/Dialect/SparseTensor/CPU/sparse_sum.mlir Thu, 14 Jul 2022 07:47:37 +0000 Matthias Springer <springerm@google.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/mlir/test/Integration/Dialect/SparseTensor/CPU/sparse_sum.mlir#a6cef03f [mlir] Remove the `type` keyword from type alias definitionsThis was carry over from LLVM IR where the alias definition canbe ambiguous, but MLIR type aliases have no such problems.Having the `type` keyword is superfluous and doesn't add anything.This commit drops it, which also nicely aligns with the syntax forattribute aliases (which doesn't have a keyword).Differential Revision: https://reviews.llvm.org/D125501 List of files: /llvm-project-15.0.7/mlir/test/Integration/Dialect/SparseTensor/CPU/sparse_sum.mlir Thu, 12 May 2022 20:36:05 +0000 River Riddle <riddleriver@gmail.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/mlir/test/Integration/Dialect/SparseTensor/CPU/sparse_sum.mlir#4620032e Revert "[mlir][sparse] Expose SpareTensor passes as enums instead of opaque numbers for vectorization and parallelization options."This reverts commit d59cf901cbae7991f7847eb038d825efff1221ad.Build fails on NVIDIA Sparse tests:https://lab.llvm.org/buildbot/#/builders/61/builds/25447 List of files: /llvm-project-15.0.7/mlir/test/Integration/Dialect/SparseTensor/CPU/sparse_sum.mlir Sun, 24 Apr 2022 01:14:48 +0000 Nick Kreeger <nick.kreeger@gmail.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/mlir/test/Integration/Dialect/SparseTensor/CPU/sparse_sum.mlir#d59cf901 [mlir][sparse] Expose SpareTensor passes as enums instead of opaque numbers for vectorization and parallelization options.The SparseTensor passes currently use opaque numbers for the CLI, despite using an enum internally. This patch exposes the enums instead of numbered items that are matched back to the enum.Fixes GitHub issue #53389Reviewed by: aartbik, mehdi_aminiDifferential Revision: https://reviews.llvm.org/D123876 List of files: /llvm-project-15.0.7/mlir/test/Integration/Dialect/SparseTensor/CPU/sparse_sum.mlir Sun, 24 Apr 2022 00:16:57 +0000 Nick Kreeger <nick.kreeger@gmail.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/mlir/test/Integration/Dialect/SparseTensor/CPU/sparse_sum.mlir#87db8e44 [mlir][NFC] Update textual references of `func` to `func.func` in Integration testsThe special case parsing of `func` operations is being removed. List of files: /llvm-project-15.0.7/mlir/test/Integration/Dialect/SparseTensor/CPU/sparse_sum.mlir Wed, 20 Apr 2022 23:20:21 +0000 River Riddle <riddleriver@gmail.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/mlir/test/Integration/Dialect/SparseTensor/CPU/sparse_sum.mlir#b85ed4e0 [mlir][sparse] Adding standard pipeline for tests.Addresses https://bugs.llvm.org/show_bug.cgi?id=52409 aka https://github.com/llvm/llvm-project/issues/51751Reviewed By: aartbik, mehdi_aminiDifferential Revision: https://reviews.llvm.org/D117919 List of files: /llvm-project-15.0.7/mlir/test/Integration/Dialect/SparseTensor/CPU/sparse_sum.mlir Thu, 27 Jan 2022 00:44:32 +0000 wren romano <2998727+wrengr@users.noreply.github.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/mlir/test/Integration/Dialect/SparseTensor/CPU/sparse_sum.mlir#57470abc [mlir] Move memref.[tensor_load|buffer_cast|clone] to "bufferization" dialect.https://llvm.discourse.group/t/rfc-dialect-for-bufferization-related-ops/4712Differential Revision: https://reviews.llvm.org/D114552 List of files: /llvm-project-15.0.7/mlir/test/Integration/Dialect/SparseTensor/CPU/sparse_sum.mlir Thu, 25 Nov 2021 10:42:16 +0000 Alexander Belyaev <pifon@google.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/mlir/test/Integration/Dialect/SparseTensor/CPU/sparse_sum.mlir#02710413 Accept symmetric sparse matrix in Matrix Market Exchange Format.Reviewed By: aartbikDifferential Revision: https://reviews.llvm.org/D114402 List of files: /llvm-project-15.0.7/mlir/test/Integration/Dialect/SparseTensor/CPU/sparse_sum.mlir Mon, 22 Nov 2021 23:24:52 +0000 Bixia Zheng <bixia@google.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/mlir/test/Integration/Dialect/SparseTensor/CPU/sparse_sum.mlir#38c366e4 [mlir][sparse] run more integration tests with and without SIMDReviewed By: wrengrDifferential Revision: https://reviews.llvm.org/D113205 List of files: /llvm-project-15.0.7/mlir/test/Integration/Dialect/SparseTensor/CPU/sparse_sum.mlir Thu, 04 Nov 2021 17:28:32 +0000 Aart Bik <ajcbik@google.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/mlir/test/Integration/Dialect/SparseTensor/CPU/sparse_sum.mlir#a54f4eae [MLIR] Replace std ops with arith dialect opsPrecursor: https://reviews.llvm.org/D110200Removed redundant ops from the standard dialect that were moved to the`arith` or `math` dialects.Renamed all instances of operations in the codebase and in tests.Reviewed By: rriddle, jpienaarDifferential Revision: https://reviews.llvm.org/D110797 List of files: /llvm-project-15.0.7/mlir/test/Integration/Dialect/SparseTensor/CPU/sparse_sum.mlir Tue, 12 Oct 2021 23:14:57 +0000 Mogball <jeffniu22@gmail.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/mlir/test/Integration/Dialect/SparseTensor/CPU/sparse_sum.mlir#16b8f4dd [mlir][sparse] add a "release" operation to sparse tensor dialectWe have several ways to materialize sparse tensors (new and convert) but no explicit operation to release the underlying sparse storage scheme at runtime (other than making an explicit delSparseTensor() library call). To simplify memory management, a sparse_tensor.release operation has been introduced that lowers to the runtime library call while keeping tensors, opague pointers, and memrefs transparent in the initial IR.*Note* There is obviously some tension between the concept of immutable tensors and memory management methods. This tension is addressed by simply stating that after the "release" call, no further memref related operations are allowed on the tensor value. We expect the design to evolve over time, however, and arrive at a more satisfactory view of tensors and buffers eventually.Bug:http://llvm.org/pr52046Reviewed By: bixiaDifferential Revision: https://reviews.llvm.org/D111099 List of files: /llvm-project-15.0.7/mlir/test/Integration/Dialect/SparseTensor/CPU/sparse_sum.mlir Mon, 04 Oct 2021 20:13:24 +0000 Aart Bik <ajcbik@google.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/mlir/test/Integration/Dialect/SparseTensor/CPU/sparse_sum.mlir#8b58ab8c [mlir] Factor type reconciliation out of Standard-to-LLVM conversionConversion to the LLVM dialect is being refactored to be more progressive andis now performed as a series of independent passes converting differentdialects. These passes may produce `unrealized_conversion_cast` operations thatrepresent pending conversions between built-in and LLVM dialect types.Historically, a more monolithic Standard-to-LLVM conversion pass did not needthese casts as all operations were converted in one shot. Previous refactoringshave led to the requirement of running the Standard-to-LLVM conversion pass toclean up `unrealized_conversion_cast`s even though the IR had no standardoperations in it. The pass must have been also run the last among all to-LLVMpasses, in contradiction with the partial conversion logic. Additionally, theway it was set up could produce invalid operations by removing casts betweenLLVM and built-in types even when the consumer did not accept the uncastedtype, or could lead to cryptic conversion errors (recursive application of therewrite pattern on `unrealized_conversion_cast` as a means to indicate failureto eliminate casts).In fact, the need to eliminate A->B->A `unrealized_conversion_cast`s is notspecific to to-LLVM conversions and can be factored out into a separate typereconciliation pass, which is achieved in this commit. While the cast operationitself has a folder pattern, it is insufficient in most conversion passes asthe folder only applies to the second cast. Without complex legality setup inthe conversion target, the conversion infra will either consider the castoperations valid and not fold them (a separate canonicalization would benecessary to trigger the folding), or consider the first cast invalid upongeneration and stop with error. The pattern provided by the reconciliation passapplies to the first cast operation instead. Furthermore, having a separatepass makes it clear when `unrealized_conversion_cast`s could not have beeneliminated since it is the only reason why this pass can fail.Reviewed By: nicolasvasilacheDifferential Revision: https://reviews.llvm.org/D109507 List of files: /llvm-project-15.0.7/mlir/test/Integration/Dialect/SparseTensor/CPU/sparse_sum.mlir Thu, 09 Sep 2021 14:06:10 +0000 Alex Zinenko <zinenko@google.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/mlir/test/Integration/Dialect/SparseTensor/CPU/sparse_sum.mlir#2b013a6c [mlir][sparse] use proper type alias for filename ptrReviewed By: gussmith23Differential Revision: https://reviews.llvm.org/D106904 List of files: /llvm-project-15.0.7/mlir/test/Integration/Dialect/SparseTensor/CPU/sparse_sum.mlir Tue, 27 Jul 2021 18:41:49 +0000 Aart Bik <ajcbik@google.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/mlir/test/Integration/Dialect/SparseTensor/CPU/sparse_sum.mlir#e6e79b3f [mlir][sparse] remove linalg-to-loops from integration testsWith the migration from linalg.copy to memref.copy, this pass(which was there solely to handle the linalg.copy op) is nolonger required for the end-to-end path for sparse compilation.Reviewed By: ftynseDifferential Revision: https://reviews.llvm.org/D106073 List of files: /llvm-project-15.0.7/mlir/test/Integration/Dialect/SparseTensor/CPU/sparse_sum.mlir Thu, 15 Jul 2021 15:40:31 +0000 Aart Bik <ajcbik@google.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/mlir/test/Integration/Dialect/SparseTensor/CPU/sparse_sum.mlir#75e5f0aa [mlir] factor memref-to-llvm lowering out of std-to-llvmAfter the MemRef has been split out of the Standard dialect, theconversion to the LLVM dialect remained as a huge monolithic pass.This is undesirable for the same complexity management reasons as havinga huge Standard dialect itself, and is even more confusing given theexistence of a separate dialect. Extract the conversion of the MemRefdialect operations to LLVM into a separate library and a separateconversion pass.Reviewed By: herhut, silvasDifferential Revision: https://reviews.llvm.org/D105625 List of files: /llvm-project-15.0.7/mlir/test/Integration/Dialect/SparseTensor/CPU/sparse_sum.mlir Thu, 08 Jul 2021 16:35:18 +0000 Alex Zinenko <zinenko@google.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/mlir/test/Integration/Dialect/SparseTensor/CPU/sparse_sum.mlir#96a23911 [mlir][sparse] complete migration to sparse tensor typeA very elaborate, but also very fun revision because allpuzzle pieces are finally "falling in place".1. replaces lingalg annotations + flags with proper sparse tensor types2. add rigorous verification on sparse tensor type and sparse primitives3. removes glue and clutter on opaque pointers in favor of sparse tensor types4. migrates all tests to use sparse tensor typesNOTE: next CL will remove *all* obsoleted sparse code in LinalgReviewed By: bixiaDifferential Revision: https://reviews.llvm.org/D102095 List of files: /llvm-project-15.0.7/mlir/test/Integration/Dialect/SparseTensor/CPU/sparse_sum.mlir Mon, 10 May 2021 17:34:21 +0000 Aart Bik <ajcbik@google.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/mlir/test/Integration/Dialect/SparseTensor/CPU/sparse_sum.mlir#a2c9d4bb [mlir][sparse] Introduce proper sparsification passesThis revision migrates more code from Linalg into the new permanent home ofSparseTensor. It replaces the test passes with proper compiler passes.NOTE: the actual removal of the last glue and clutter in Linalg will followReviewed By: bixiaDifferential Revision: https://reviews.llvm.org/D101811 List of files: /llvm-project-15.0.7/mlir/test/Integration/Dialect/SparseTensor/CPU/sparse_sum.mlir Tue, 04 May 2021 03:55:12 +0000 Aart Bik <ajcbik@google.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/mlir/test/Integration/Dialect/SparseTensor/CPU/sparse_sum.mlir#319072f4 [mlir][sparse] migrate sparse operations into new sparse tensor dialectThis is the very first step toward removing the glue and clutter from linalg andreplace it with proper sparse tensor types. This revision migrates the LinalgSparseOpsinto SparseTensorOps of a sparse tensor dialect. This also provides a new home forsparse tensor related transformation.NOTE: the actual replacement with sparse tensor types (and removal of linalg glue/clutter)will follow but I am trying to keep the amount of changes per revision manageable.Differential Revision: https://reviews.llvm.org/D101573 List of files: /llvm-project-15.0.7/mlir/test/Integration/Dialect/SparseTensor/CPU/sparse_sum.mlir Thu, 29 Apr 2021 21:31:18 +0000 Aart Bik <ajcbik@google.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/mlir/test/Integration/Dialect/SparseTensor/CPU/sparse_sum.mlir#a6d92a97 [mlir][sparse] migrate sparse operations into new sparse tensor dialectThis is the very first step toward removing the glue and clutter from linalg andreplace it with proper sparse tensor types. This revision migrates the LinalgSparseOpsinto SparseTensorOps of a sparse tensor dialect. This also provides a new home forsparse tensor related transformation.NOTE: the actual replacement with sparse tensor types (and removal of linalg glue/clutter)will follow but I am trying to keep the amount of changes per revision manageable.Reviewed By: bixiaDifferential Revision: https://reviews.llvm.org/D101488 List of files: /llvm-project-15.0.7/mlir/test/Integration/Dialect/SparseTensor/CPU/sparse_sum.mlir Thu, 29 Apr 2021 01:15:11 +0000 Aart Bik <ajcbik@google.com>