maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/mlir/tools/CMakeLists.txt

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

15 lines
440 B
CMake
Raw Normal View History

[mlir][mlir-lsp] Add a new C++ LSP server for MLIR named mlir-lsp-server This commits adds a basic LSP server for MLIR that supports resolving references and definitions. Several components of the setup are simplified to keep the size of this commit down, and will be built out in later commits. A followup commit will add a vscode language client that communicates with this server, paving the way for better IDE experience when interfacing with MLIR files. The structure of this tool is similar to mlir-opt and mlir-translate, i.e. the implementation is structured as a library that users can call into to implement entry points that contain the dialects/passes that they are interested in. Note: This commit contains several files, namely those in `mlir-lsp-server/lsp`, that have been copied from the LSP code in clangd and adapted for use in MLIR. This copying was decided as the best initial path forward (discussed offline by several stake holders in MLIR and clangd) given the different needs of our MLIR server, and the one for clangd. If a strong desire/need for unification arises in the future, the existence of these files in mlir-lsp-server can be reconsidered. Differential Revision: https://reviews.llvm.org/D100439
2021-04-22 05:33:04 +08:00
add_subdirectory(mlir-lsp-server)
Add build files and update README. * Add initial version of build files; * Update README with instructions to download and build MLIR from github; -- PiperOrigin-RevId: 241102092
2019-03-30 13:10:12 +08:00
add_subdirectory(mlir-opt)
[mlir][PDLL] Add an initial frontend for PDLL This is a new pattern rewrite frontend designed from the ground up to support MLIR constructs, and to target PDL. This frontend language was proposed in https://llvm.discourse.group/t/rfc-pdll-a-new-declarative-rewrite-frontend-for-mlir/4798 This commit starts sketching out the base structure of the frontend, and is intended to be a minimal starting point for building up the language. It essentially contains support for defining a pattern, variables, and erasing an operation. The features mentioned in the proposal RFC (including IDE support) will be added incrementally in followup commits. I intend to upstream the documentation for the language in a followup when a bit more of the pieces have been landed. Differential Revision: https://reviews.llvm.org/D115093
2021-12-16 09:48:19 +08:00
add_subdirectory(mlir-pdll)
Create the MLIR Reduce framework Create the framework and testing environment for MLIR Reduce - a tool with the objective to reduce large test cases into smaller ones while preserving their interesting behavior. Implement the functionality to parse command line arguments, parse the MLIR test cases into modules and run the interestingness tests on the modules. Reviewed By: jpienaar Differential Revision: https://reviews.llvm.org/D82803
2020-07-08 07:42:40 +08:00
add_subdirectory(mlir-reduce)
Revert "Create the framework and testing environment for MLIR Reduce - a tool" This reverts commit 28a45d54a7fe722248233165fc7fdbd18d18d233. Windows bot is broken with: LLVM ERROR: Error running interestingness test: posix_spawn failed: Permission denied
2020-07-07 23:46:06 +08:00
add_subdirectory(mlir-shlib)
[MLIR][mlir-spirv-cpu-runner] A SPIR-V cpu runner prototype This patch introduces a SPIR-V runner. The aim is to run a gpu kernel on a CPU via GPU -> SPIRV -> LLVM conversions. This is a first prototype, so more features will be added in due time. - Overview The runner follows similar flow as the other runners in-tree. However, having converted the kernel to SPIR-V, we encode the bind attributes of global variables that represent kernel arguments. Then SPIR-V module is converted to LLVM. On the host side, we emulate passing the data to device by creating in main module globals with the same symbolic name as in kernel module. These global variables are later linked with ones from the nested module. We copy data from kernel arguments to globals, call the kernel function from nested module and then copy the data back. - Current state At the moment, the runner is capable of running 2 modules, nested one in another. The kernel module must contain exactly one kernel function. Also, the runner supports rank 1 integer memref types as arguments (to be scaled). - Enhancement of JitRunner and ExecutionEngine To translate nested modules to LLVM IR, JitRunner and ExecutionEngine were altered to take an optional (default to `nullptr`) function reference that is a custom LLVM IR module builder. This allows to customize LLVM IR module creation from MLIR modules. Reviewed By: ftynse, mravishankar Differential Revision: https://reviews.llvm.org/D86108
2020-10-23 22:46:18 +08:00
add_subdirectory(mlir-spirv-cpu-runner)
Create the MLIR Reduce framework Create the framework and testing environment for MLIR Reduce - a tool with the objective to reduce large test cases into smaller ones while preserving their interesting behavior. Implement the functionality to parse command line arguments, parse the MLIR test cases into modules and run the interestingness tests on the modules. Reviewed By: jpienaar Differential Revision: https://reviews.llvm.org/D82803
2020-07-08 07:42:40 +08:00
add_subdirectory(mlir-translate)
[mlir] Fix cross-compilation (Linalg ODS gen) Use cross-compilation approach for `mlir-linalg-ods-gen` application similar to TblGen tools. Reviewed By: nicolasvasilache Differential Revision: https://reviews.llvm.org/D94598
2021-01-18 18:54:06 +08:00
add_subdirectory(mlir-vulkan-runner)
[mlir] Only build mlir-cpu-runner when the native arch is targeted mlir-cpu-runner has a dependency on ExecutionEngine which is only built for the native arch. So currently mlir-cpu-runner does not link correctly when the native arch is not targeted. Reviewed By: mehdi_amini Differential Revision: https://reviews.llvm.org/D118422
2022-01-29 02:09:09 +08:00
# mlir-cpu-runner requires ExecutionEngine which is only built
# when the native target is configured in.
if(TARGET ${LLVM_NATIVE_ARCH})
add_subdirectory(mlir-cpu-runner)
endif()