[llvm-lsp] LSP server for LLVM IR #161969
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Co-authored-by: Nikita Popov <[email protected]>
|
|
|
✅ With the latest revision this PR passed the C/C++ code formatter. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is part of the LLVM IR LSP server project (RFC)
This PR depends on #155797
With this PR we are introducing a LSP server for LLVM IR as the
llvm-lsp-servertool.The LSP is build using the LSP support library, that was recently moved from MLIR into Support/LSP. And supports some standard LSP messages as well as some custom ones tailored for compiler development.
The server supports the following standard LSP capabilities:
textDocumentSync.openClose: Synchronizes document content with the server.referencesProvider: Finds all references to a symbol.codeActionProvider: Provides code actions, such as quick fixes and refactorings. This server uses it to provide CFG views.documentsSymbolProvider: Provides a tree of document symbols, enables breadcrums navigation in the editor.Non-standard messages are used for
How is the LSP server build
The server utilizes a similar build to the LSP servers found in MLIR or clangd.
Open files use a support class IRDocument, this class handles anything involving the file directly.
To enable cross navigation between CFG and IR a parameter was added to the DOTFuncInfo, a function that takes a BasicBlock and returns a string id for that basicblock.
For running optimization pipelines, the PassManager API is used.
LSP artifacts like CFGs and optimized files are then stored in a folder next to the file, accessible to the user. Optimization create a subfolder in the artifacts folder.