[mlir][sparse] fix windows build errorSilence warning from MSVC when handling ##__VA_ARGSReviewed By: aartbikDifferential Revision: https://reviews.llvm.org/D129227
Revert "[mlir][sparse] add more unittest cases to sparse dialect merger"This broke the windows mlir bot: https://lab.llvm.org/buildbot/#/builders/13/builds/22743This reverts commit daeb2dcea09820
Revert "[mlir][sparse] add more unittest cases to sparse dialect merger"This broke the windows mlir bot: https://lab.llvm.org/buildbot/#/builders/13/builds/22743This reverts commit daeb2dcea09820d92f81db84623cf1c6df825e14 and 537db49596f65a05c0309cf3333fc44f1657e999.
show more ...
[mlir][sparse] Silencing some -Wunused-function in unittestsThis is a followup to D128058.Reviewed By: aartbikDifferential Revision: https://reviews.llvm.org/D129027
[mlir][sparse] add more unittest cases to sparse dialect mergerReviewed By: aartbik, wrengrDifferential Revision: https://reviews.llvm.org/D128058
[mlir][sparse] refactor handling of merger leafs and opsUsing "default:" in the switch statemements that handle all ourmerger ops has become a bit cumbersome since it is easy to overlookparts of
[mlir][sparse] refactor handling of merger leafs and opsUsing "default:" in the switch statemements that handle all ourmerger ops has become a bit cumbersome since it is easy to overlookparts of the code that need to handle ops specifically. By enforcingfull switch statements without "default:", we get a compiler warningwhen cases are overlooked.Reviewed By: wrengrDifferential Revision: https://reviews.llvm.org/D127263
[mlir][NFC] Add a using for llvm::SMLoc/llvm::SMRange to LLVM.hThese are used pervasively during parsing.Differential Revision: https://reviews.llvm.org/D118291
[mlir][NFC] Add a using for llvm::BitVector to LLVM.hBitVector is becoming widespread enough that we should add a proper using.Differential Revision: https://reviews.llvm.org/D118290
Apply clang-tidy fixes for performance-unnecessary-value-param to MLIR (NFC)
Apply clang-tidy fixes for performance-unnecessary-value-param to MLIR (NFC)Reviewed By: MogballDifferential Revision: https://reviews.llvm.org/D116250
Adjust "end namespace" comment in MLIR to match new agree'd coding styleSee D115115 and this mailing list discussion:https://lists.llvm.org/pipermail/llvm-dev/2021-December/154199.htmlDifferenti
Adjust "end namespace" comment in MLIR to match new agree'd coding styleSee D115115 and this mailing list discussion:https://lists.llvm.org/pipermail/llvm-dev/2021-December/154199.htmlDifferential Revision: https://reviews.llvm.org/D115309
[mlir][sparse] add support for std unary operationsAdds zero-preserving unary operators from std. Also adds xor.Performs minor refactoring to remove "zero" node, and pushedthe irregular logic for
[mlir][sparse] add support for std unary operationsAdds zero-preserving unary operators from std. Also adds xor.Performs minor refactoring to remove "zero" node, and pushedthe irregular logic for negi (not support in std) into one place.Reviewed By: gussmith23Differential Revision: https://reviews.llvm.org/D105928
[mlir][sparse] Add Merger unit tests (with gcc5 build fix)This is a fix of https://reviews.llvm.org/D104956, which broke the gcc5 build.We opt to use unit tests rather than check tests as the lat
[mlir][sparse] Add Merger unit tests (with gcc5 build fix)This is a fix of https://reviews.llvm.org/D104956, which broke the gcc5 build.We opt to use unit tests rather than check tests as the lattice/merger code is a small C++ component with a well-defined API. Testing this API via check tests would be far less direct and readable. In addition, as the check tests will only be able to test the API indirectly, the tests may break based on unrelated changes; e.g. changes in linalg.Reviewed By: aartbikDifferential Revision: https://reviews.llvm.org/D105828
Revert "[mlir][sparse] Add Merger unit tests"This reverts commit 0d0cff3ace39378acfc66d6564dc99e19b8a561f.The build is broken with GCC 5.4
[mlir][sparse] Add Merger unit testsWe opt to use unit tests rather than check tests as the lattice/merger code is a small C++ component with a well-defined API. Testing this API via check tests wo
[mlir][sparse] Add Merger unit testsWe opt to use unit tests rather than check tests as the lattice/merger code is a small C++ component with a well-defined API. Testing this API via check tests would be far less direct and readable. In addition, as the check tests will only be able to test the API indirectly, the tests may break based on unrelated changes; e.g. changes in linalg.Reviewed By: aartbikDifferential Revision: https://reviews.llvm.org/D104956