| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
[mlir:vscode] Add support for loading big bytecode files VSCode doesn't let our extension manage files >50mb. This commit adds a proper diagnostic in this case, and also gives the user an option to open as a temporary .mlir file instead. Differential Revision: https://reviews.llvm.org/D133242 | 3 年前 | |
[mlir:vscode] Add support for viewing and editing a bytecode file as .mlir This commit adds support for interacting with a (valid) bytecode file in the same way as .mlir. This allows editing, using all of the traditional LSP features, etc. but still using bytecode as the on-disk serialization format. Loading a bytecode file this way will fail if the bytecode is invalid, and saving will fail if the edited .mlir is invalid. Differential Revision: https://reviews.llvm.org/D132970 | 3 年前 | |
[mlir:PDLL-LSP] Add a custom LSP command for viewing the output of PDLL This commit adds a new PDLL specific LSP command, pdll.viewOutput, that allows for viewing the intermediate outputs of a given PDLL file. The available intermediate forms currently mirror those in mlir-pdll, namely: AST, MLIR, CPP. This is extremely useful for a developer of PDLL, as it simplifies various testing, and is also quite useful for users as they can easily view what is actually being generated for their PDLL files. This new command is added to the vscode client, and is available in the right client context menu of PDLL files, or via the vscode command palette. Differential Revision: https://reviews.llvm.org/D124783 | 4 年前 | |
[mlir][Tablegen-LSP] Add support for a compilation database This provides a format for externally specifying the include directories for a source file. The format of the tablegen database is exactly the same as that for PDLL, namely it includes the absolute source file name and the set of include directories. The database format is shared to simplify the infra, and also because the format itself is general enough to share. Even if we desire to expand in the future to contain the actual compilation command, nothing there is specific enough that we would need two different formats. As with PDLL, support for generating the database is added to our mlir_tablegen cmake command. Differential Revision: https://reviews.llvm.org/D125441 | 4 年前 | |
[mlir][PDLL] Add initial support for a PDLL compilation database The compilation database acts in a similar way to the compilation database (compile_commands.json) used by clang-tidy, i.e. it provides additional information about the compilation of project files to help the language server. The main piece of information provided by the PDLL compilation database in this commit is the set of include directories used when processing the input .pdll file. This allows for the server to properly process .pdll files that use includes anchored by the include directories set up in the build system. The structure of the textual form of a compilation database is a yaml file containing documents of the following form: --- !FileInfo: filepath: <string> - Absolute file path of the file. includes: <string> - Semi-colon delimited list of include directories. This commit also adds support to cmake for automatically generating a pdll_compile_commands.yml file at the top-level of the build directory. Differential Revision: https://reviews.llvm.org/D124076 | 4 年前 | |
[mlir:vscode] Add support for viewing and editing a bytecode file as .mlir This commit adds support for interacting with a (valid) bytecode file in the same way as .mlir. This allows editing, using all of the traditional LSP features, etc. but still using bytecode as the on-disk serialization format. Loading a bytecode file this way will fail if the bytecode is invalid, and saving will fail if the edited .mlir is invalid. Differential Revision: https://reviews.llvm.org/D132970 | 3 年前 | |
[vscode-mlir] Added per-LSP-server executable arguments (#79671) Each LSP server type (mlir-lsp-server, pdll-lsp-server and tblgen-lsp-server) should have a different "additional_server_args" entry in the config for passing arguments to the server such as --log=verbose. | 1 年前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 3 年前 | ||
| 3 年前 | ||
| 4 年前 | ||
| 4 年前 | ||
| 4 年前 | ||
| 3 年前 | ||
| 1 年前 |