en Copyright 2015 Java http://172.16.0.5:8080/history/llvm-project-15.0.7/mlir/test/Integration/Dialect/SparseTensor/CPU/sparse_matrix_ops.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_matrix_ops.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_matrix_ops.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_matrix_ops.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_matrix_ops.mlir#6232a8f3 [mlir][sparse][NFC] Switch InitOp to bufferization::AllocTensorOpNow that we have an AllocTensorOp (previously InitTensorOp) in the bufferization dialect, the InitOp in the sparse dialect is no longer needed.Differential Revision: https://reviews.llvm.org/D126180 List of files: /llvm-project-15.0.7/mlir/test/Integration/Dialect/SparseTensor/CPU/sparse_matrix_ops.mlir Wed, 01 Jun 2022 21:59:58 +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_matrix_ops.mlir#2c332660 [mlir][sparse] Add lowering for unary and binary opsAdding lowering for Unary and Binary required several changes due totheir unique nature of containing custom code for different "regions"of the sparse structure being operated on. Along with a Kind, a pointerto the Operation is passed along to be merged once the latticestructure is figured out.The original operation is maintained, as it is required for subsequentlattice decisions. However, sparse_tensor.binary has some branchesare considered as fully handled and therefore are marked with askBinaryBranch to distinguish them.A unique aspect of the custom code is that sometimes the desired resultis no result at all -- i.e. a user wants overlapping sparse entries tobecome empty in the output. The solution to this is to return anuninitialized Value(), which is checked and handled elsewhere in thecode and results in nothing being written to the output tensor for thatcase.Reviewed By: aartbikDifferential Revision: https://reviews.llvm.org/D123057 List of files: /llvm-project-15.0.7/mlir/test/Integration/Dialect/SparseTensor/CPU/sparse_matrix_ops.mlir Tue, 03 May 2022 20:50:26 +0000 Jim Kitchen <jim22k@gmail.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/mlir/test/Integration/Dialect/SparseTensor/CPU/sparse_matrix_ops.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_matrix_ops.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_matrix_ops.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_matrix_ops.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_matrix_ops.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_matrix_ops.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_matrix_ops.mlir#1ce77b56 [mlir][sparse] refine lexicographic insertion to any tensorFirst version was vectors only. With some clever "path" insertion,we now support any d-dimensional tensor. Up next: reductions tooReviewed By: bixia, wrengrDifferential Revision: https://reviews.llvm.org/D114024 List of files: /llvm-project-15.0.7/mlir/test/Integration/Dialect/SparseTensor/CPU/sparse_matrix_ops.mlir Tue, 16 Nov 2021 20:46:55 +0000 Aart Bik <ajcbik@google.com>