en Copyright 2015 Java http://172.16.0.5:8080/history/llvm-project-15.0.7/mlir/test/Integration/Dialect/SparseTensor/CPU/sparse_quantized_matmul.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_quantized_matmul.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_quantized_matmul.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_quantized_matmul.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_quantized_matmul.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_quantized_matmul.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_quantized_matmul.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_quantized_matmul.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_quantized_matmul.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_quantized_matmul.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_quantized_matmul.mlir#515c6170 [mlir][linalg][sparse] add linalg optimization passes "upstream"It is time to compose Linalg related optimizations with SparseTensorrelated optimizations. This is a careful first start by adding somegeneral Linalg optimizations "upstream" of the sparse compiler in thefull sparse compiler pipeline. Some minor changes were needed to makethose optimizations aware of sparsity.Note that after this, we will add a sparse specific fusion rule,just to demonstrate the power of the new composition.Reviewed By: bixiaDifferential Revision: https://reviews.llvm.org/D119971 List of files: /llvm-project-15.0.7/mlir/test/Integration/Dialect/SparseTensor/CPU/sparse_quantized_matmul.mlir Wed, 16 Feb 2022 20:56:43 +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_quantized_matmul.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_quantized_matmul.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_quantized_matmul.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_quantized_matmul.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_quantized_matmul.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_quantized_matmul.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_quantized_matmul.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_quantized_matmul.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_quantized_matmul.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_quantized_matmul.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_quantized_matmul.mlir#a924fcc7 [mlir][sparse] add sparse kernels test to sparse compiler test suiteThis test makes sure kernels map to efficient sparse code, i.e. allcompressed for-loops, no co-iterating while loops. In addition, thisrevision removes the special constant folding inside the sparsecompiler in favor of Mahesh' new generic linalg folding. Thanks!NOTE: relies on Mahesh fix, which needs to be rebased firstReviewed By: bixiaDifferential Revision: https://reviews.llvm.org/D110001 List of files: /llvm-project-15.0.7/mlir/test/Integration/Dialect/SparseTensor/CPU/sparse_quantized_matmul.mlir Mon, 20 Sep 2021 18:15:13 +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_quantized_matmul.mlir#46e77b5d [mlir][sparse] add a sparse quantized_matmul example to integration testNote that this revision adds a very tiny bit of constant folding in thesparse compiler lattice construction. Although I am generally trying toavoid such canonicalizations (and rely on other passes to fix this instead),the benefits of avoiding a very expensive disjunction lattice constructionjustify having this special code (at least for now).Reviewed By: bixiaDifferential Revision: https://reviews.llvm.org/D109939 List of files: /llvm-project-15.0.7/mlir/test/Integration/Dialect/SparseTensor/CPU/sparse_quantized_matmul.mlir Thu, 16 Sep 2021 23:43:03 +0000 Aart Bik <ajcbik@google.com>