Neovim configuration for RISC-V Assembly

[irtaza-10x]

Hi there, I recently started working with riscv asm and have been facing issues configuring the asm-lsp properly with my project.

Issues

Autocompletion and Reference

Pseudo Instructions

The Autocompletion for RISC-V pseudo-instructions does not seem to work. I tried to print reference for the la command but it threw the following error. A problem is also observed with macro completion and definition, the LSP error with id=46 when trying to print macro reference.

However running it on a RISC-V base command displays the desired result.

ABI Register Names

The LSP only seems to autocomplete and show definition of registers using the x0-x31 format. Names such as zero or mcause do not generate a diagnostic error but cause issues when trying to see their reference.

Error Message Indentation

The diagnostic messages appear at a weird offset from the actual erroneous line

Goto Definitions

Using gd on the label .L_test_failed gives the following error. A similar error is thrown when trying to goto macro definition with id=45

Cannot open file

Even though I have specified my path = "src/" in .asm-lsp.toml, it gives me the following error message: Cannot open macro.S for reading, No such file or directory found. But when change the .include macro.S to .include src/macro.S is seems to work.

Environment

I have installed asm-lsp on Neovim using :Mason. It shows that that version 0.10.0 is installed. Using :LspInfo shows the following:

vim.lsp: Active Clients ~
- asm_lsp (id: 1)
  - Version: ? (no serverInfo.version response)
  - Root directory: <PATH_TO_CURRENT_DIR>
  - Command: { "asm-lsp" }
  - Settings: {}
  - Attached buffers: 

My .asm-lsp.toml generated using the asm-lsp gen-config for the project is as follows:

[[project]]
path = "src"
version = "0.10.0"
assembler = "gas"
instruction_set = "riscv"

[project.opts]
compiler = "riscv64-unknown-elf-gcc"
compile_flags_txt = [
    '"-T riscv.ld"',
    "-nostdlib",
    "-march=rv32im_zicsr",
    "-mabi=ilp32",
]
diagnostics = true
default_diagnostics = false

The following is my directory structure based on the specification I have to work with:

.
├── Makefile
├── README.md
└── src
    ├── lib.s
    ├── macro.s
    ├── main.s
    ├── regs.s
    ├── riscv.ld
    ├── startup.s
    ├── syscalls.s
    └── trap.s

My git directory is 2 stages above the projects root directory. I did try to do git init in my current project directory but the above issues still persist.

Let me know if any additional information such as the :LspLog or my global .asm-lsp.toml is required.

Update: I have also added a compile_commands.json using bear -- riscv64-unknown-elf-gcc -T src/riscv.ld -nostdlib -march=rv32im_zicsr -mabi-ilp32 src/* -o build/main. The contents of the ./compile_commands.json are as follows:

[
  {
    "arguments": [
      "~/Desktop/Tests/RISCV64/riscv64-unknown-elf-toolchain/bin/riscv64-unknown-elf-gcc",
      "-c",
      "-mabi=ilp32",
      "-march=rv32im_zicsr",
      "-o",
      "build/main",
      "src/lib.S"
    ],
    "directory": "~/Desktop/Tests/current_dir",
    "file": "~/Desktop/Tests/current_dir/src/lib.S",
    "output": "~/Desktop/Tests/current_dir/build/main"
  },
  {
    "arguments": [
      "~/Desktop/Tests/RISCV64/riscv64-unknown-elf-toolchain/bin/riscv64-unknown-elf-gcc",
      "-c",
      "-mabi=ilp32",
      "-march=rv32im_zicsr",
      "-o",
      "build/main",
      "src/macro.S"
    ],
    "directory": "~/Desktop/Tests/current_dir",
    "file": "~/Desktop/Tests/current_dir/src/macro.S",
    "output": "~/Desktop/Tests/current_dir/build/main"
  },
  {
    "arguments": [
      "~/Desktop/Tests/RISCV64/riscv64-unknown-elf-toolchain/bin/riscv64-unknown-elf-gcc",
      "-c",
      "-mabi=ilp32",
      "-march=rv32im_zicsr",
      "-o",
      "build/main",
      "src/main.S"
    ],
    "directory": "~/Desktop/Tests/current_dir",
    "file": "~/Desktop/Tests/current_dir/src/main.S",
    "output": "~/Desktop/Tests/current_dir/build/main"
  },
  {
    "arguments": [
      "~/Desktop/Tests/RISCV64/riscv64-unknown-elf-toolchain/bin/riscv64-unknown-elf-gcc",
      "-c",
      "-mabi=ilp32",
      "-march=rv32im_zicsr",
      "-o",
      "build/main",
      "src/regs.S"
    ],
    "directory": "~/Desktop/Tests/current_dir",
    "file": "~/Desktop/Tests/current_dir/src/regs.S",
    "output": "~/Desktop/Tests/current_dir/build/main"
  },
  {
    "arguments": [
      "~/Desktop/Tests/RISCV64/riscv64-unknown-elf-toolchain/bin/riscv64-unknown-elf-gcc",
      "-c",
      "-mabi=ilp32",
      "-march=rv32im_zicsr",
      "-o",
      "build/main",
      "src/startup.S"
    ],
    "directory": "~/Desktop/Tests/current_dir",
    "file": "~/Desktop/Tests/current_dir/src/startup.S",
    "output": "~/Desktop/Tests/current_dir/build/main"
  },
  {
    "arguments": [
      "~/Desktop/Tests/RISCV64/riscv64-unknown-elf-toolchain/bin/riscv64-unknown-elf-gcc",
      "-c",
      "-mabi=ilp32",
      "-march=rv32im_zicsr",
      "-o",
      "build/main",
      "src/syscalls.S"
    ],
    "directory": "~/Desktop/Tests/current_dir",
    "file": "~/Desktop/Tests/current_dir/src/syscalls.S",
    "output": "~/Desktop/Tests/current_dir/build/main"
  },
  {
    "arguments": [
      "~/Desktop/Tests/RISCV64/riscv64-unknown-elf-toolchain/bin/riscv64-unknown-elf-gcc",
      "-c",
      "-mabi=ilp32",
      "-march=rv32im_zicsr",
      "-o",
      "build/main",
      "src/trap.S"
    ],
    "directory": "~/Desktop/Tests/current_dir",
    "file": "~/Desktop/Tests/current_dir/src/trap.S",
    "output": "~/Desktop/Tests/current_dir/build/main"
  }
]

[WillLillis]

The Autocompletion for RISC-V pseudo-instructions does not seem to work. I tried to print reference for the la command but it threw the following error. A problem is also observed with macro completion and definition, the LSP error with id=46 when trying to print macro reference.

All of our RISC-V related features are sourced from here, it is by no means comprehensive. The invalid message error should be resolved on the master branch by #257, but that hasn't made it into a release yet.

The diagnostic messages appear at a weird offset from the actual erroneous line

I'm not sure what's causing this.

Using gd on the label .L_test_failed gives the following error. A similar error is thrown when trying to goto macro definition with id=45

Same deal for autocomplete, this just means the server doesn't have a proper response to give. The goto definition functionality is based on a tree-sitter tree, and doesn't include semantic analysis. While improvements could definitely be made, there are some cases where it won't work.

Even though I have specified my path = "src/" in .asm-lsp.toml, it gives me the following error message: Cannot open macro.S for reading, No such file or directory found. But when change the .include macro.S to .include src/macro.S is seems to work.

This is probably a bug.

Thanks for making such a detailed report! The invalid server message issues can be addressed by using asm-lsp from the master branch. I will try to spend some time reproducing and debugging soon to address the other problems.

[tbung]

Hey, I have similar issues but with 6502 assembly/ca65. Master branch indeed made it so that hover does not create errors anymore (ref #256 ), but I'm still getting a lot of errors on autocompletion. It seems like asm-lsp is producing error up until a character is type for which autocompletion options are found:

asm_lsp: -32803: No information available
Error in TextChangedI Autocommands for "<buffer=1>":
Lua callback: vim/shared.lua:0: t: expected table, got nil
stack traceback:
	[C]: in function 'error'
	vim/shared.lua: in function 'validate'
	vim/shared.lua: in function 'tbl_contains'
	...illb/Projects/dotfiles/config/nvim/plugin/completion.lua:33: in function <...illb/Projects/dotfiles/config/nvim/plugin/completion.lua:23>
asm_lsp: -32803: No information available
Error in TextChangedI Autocommands for "<buffer=1>":
Lua callback: vim/shared.lua:0: t: expected table, got nil
stack traceback:
	[C]: in function 'error'
	vim/shared.lua: in function 'validate'
	vim/shared.lua: in function 'tbl_contains'
	...illb/Projects/dotfiles/config/nvim/plugin/completion.lua:33: in function <...illb/Projects/dotfiles/config/nvim/plugin/completion.lua:23>
asm_lsp: -32803: No information available

I am not sure how to debug this further. Here's my .asm-lsp.toml:

[default_config]
version = "0.10.0"
assembler = "ca65"
instruction_set = "6502"

[opts]
compiler = "ca65" # need "cc" as the first argument in `compile_flags.txt`
diagnostics = false
default_diagnostics = false

[[project]]
path = "emmyboot"
version = "0.10.0"
assembler = "ca65"
instruction_set = "6502"

[project.opts]
compiler = "ca65"
compile_flags_txt = [
  "cc",
"--feature",
"string_escapes",
"--cpu 65C02",
"-t",
"none",
"-m",
"build/emmyos.map",
"-C",
"emmy1.cfg"
]

[WillLillis]

@irtaza-10x I was able to reproduce the .include macro.S vs include src/macro.S locally. When I try to invoke riscv64-unknown-elf-gcc from the project's root directory, I get the same error as the error as in editor. I should note here that the path field in .asm-lsp.toml only specifies which directory of the project that config applies to, it doesn't change the root directory for the purposes of diagnostics. I see you've also added a compile_commands.json file. Using that file, asm-lsp should provide the same errors as you would get from building your project normally. If you're still seeing these errors, can I ask how you're building the project? Additionally the information from :LspLog may be helpful here.

I wasn't able to reproduce the issue with diagnostics showing up on incorrect lines, however. Do they still show up in the wrong spot after you've saved the file? (Currently, asm-lsp only provides diagnostics on save) If they're still showing up in the wrong spot, could you provide the output from invoking your compiler on the source file manually? The server provides diagnostics by invoking the compiler and parsing its output, its possible the source location for an error isn't being gathered correctly.

[irtaza-10x]

All of our RISC-V related features are sourced from here, it is by no means comprehensive. The invalid message error should be resolved on the master branch by #257, but that hasn't made it into a release yet.

Thanks for the review ^-^. I have installed asm-lsp from the master branch and configured it with nvim. The lsp errors are gone, but now it just display No information available for the pseudo-commands and ABI register names.

Same deal for autocomplete, this just means the server doesn't have a proper response to give. The goto definition functionality is based on a tree-sitter tree, and doesn't include semantic analysis. While improvements could definitely be made, there are some cases where it won't work.

For the labels starting with having format .LABEL_NAME gd displays No locations found. But for label names not starting with . it works as intended. I seems it does not work with labels resolved in another file. Could you elaborate on the what tree-sitter considers a valid goto definition and what it doesn't?

Using that file, asm-lsp should provide the same errors as you would get from building your project normally.

Yes, the same errors appear when I run the mentioned commands in compile_commands.json. I am using make run to build the project. It basically converts the .S files into .o files in build/ folder, then it further runs a command which links these object files together to produce the executable.

Probably need to generate the compile_commands.json using the makefile, but that is proving a little more challenging than I had thought and does not fit the scope of this discussion. (If someone wants to explore why, I am trying to use bear and am unable to resolve the path for the executable. This bear issue explains the issue but is for another compiler suite)

Here is the overview of the project I am currently working on:

.
├── .git
├── .asm-lsp.toml
├── Makefile
└── src
    ├── example.c
    ├── lib.s
    ├── macro.s
    ├── main.s
    ├── regs.s
    ├── riscv.ld
    ├── startup.s
    ├── syscalls.s
    └── trap.s

Here is the LspLog: information I am getting.

[ERROR][2025-10-13 10:10:17] ...nvim-linux-x86_64/share/nvim/runtime/lua/vim/lsp/log.lua:151	"rpc"	"asm-lsp"	"stderr"	"INFO [asm_lsp] Starting asm-lsp-0.10.0\n"
[ERROR][2025-10-13 10:10:17] ...nvim-linux-x86_64/share/nvim/runtime/lua/vim/lsp/log.lua:151	"rpc"	"asm-lsp"	"stderr"	'INFO [asm_lsp] Client initialization params: InitializeParams { process_id: Some(21873), root_path: Some("/home/user/Downloads/test_asm_dir"), root_uri: Some(Uri(Uri { scheme: Some("file"), authority: Some(Authority { userinfo: None, host: Host { text: "", data: RegName("") }, port: None }), path: "/home/user/Downloads/test_asm_dir", query: None, fragment: None })), initialization_options: Some(Object {}), capabilities: ClientCapabilities { workspace: Some(WorkspaceClientCapabilities { apply_edit: Some(true), workspace_edit: Some(WorkspaceEditClientCapabilities { document_changes: None, resource_operations: Some([Rename, Create, Delete]), failure_handling: None, normalizes_line_endings: Some(true), change_annotation_support: Some(ChangeAnnotationWorkspaceEditClientCapabilities { groups_on_label: Some(true) }) }), did_change_configuration: Some(DynamicRegistrationClientCapabilities { dynamic_registration: Some(false) }), did_change_watched_files: Some(DidChangeWatchedFilesClientCapabilities { dynamic_registration: Some(false), relative_pattern_support: Some(true) }), symbol: Some(WorkspaceSymbolClientCapabilities { dynamic_registration: Some(false), symbol_kind: Some(SymbolKindCapability { value_set: Some([File, Module, Namespace, Package, Class, Method, Property, Field, Constructor, Enum, Interface, Function, Variable, Constant, String, Number, Boolean, Array, Object, Key, Null, EnumMember, Struct, Event, Operator, TypeParameter]) }), tag_support: None, resolve_support: None }), execute_command: None, workspace_folders: Some(true), configuration: Some(true), semantic_tokens: Some(SemanticTokensWorkspaceClientCapabilities { refresh_support: Some(true) }), code_lens: None, file_operations: None, inline_value: None, inlay_hint: Some(InlayHintWorkspaceClientCapabilities { refresh_support: Some(true) }), diagnostic: None }), text_document: Some(TextDocumentClientCapabilities { synchronization: Some(TextDocumentSyncClientCapabilities { dynamic_registration: Some(false), will_save: Some(true), will_save_wait_until: Some(true), did_save: Some(true) }), completion: Some(CompletionClientCapabilities { dynamic_registration: Some(false), completion_item: Some(CompletionItemCapability { snippet_support: Some(true), commit_characters_support: Some(false), documentation_format: Some([Markdown, PlainText]), deprecated_support: Some(true), preselect_support: Some(false), tag_support: Some(TagSupport { value_set: [Deprecated] }), insert_replace_support: None, resolve_support: Some(CompletionItemCapabilityResolveSupport { properties: ["additionalTextEdits", "command"] }), insert_text_mode_support: None, label_details_support: None }), completion_item_kind: Some(CompletionItemKindCapability { value_set: Some([Text, Method, Function, Constructor, Field, Variable, Class, Interface, Module, Property, Unit, Value, Enum, Keyword, Snippet, Color, File, Reference, Folder, EnumMember, Constant, Struct, Event, Operator, TypeParameter]) }), context_support: Some(true), insert_text_mode: None, completion_list: Some(CompletionListCapability { item_defaults: Some(["editRange", "insertTextFormat", "insertTextMode", "data"]) }) }), hover: Some(HoverClientCapabilities { dynamic_registration: Some(true), content_format: Some([Markdown, PlainText]) }), signature_help: Some(SignatureHelpClientCapabilities { dynamic_registration: Some(false), signature_information: Some(SignatureInformationSettings { documentation_format: Some([Markdown, PlainText]), parameter_information: Some(ParameterInformationSettings { label_offset_support: Some(true) }), active_parameter_support: Some(true) }), context_support: None }), references: Some(DynamicRegistrationClientCapabilities { dynamic_registration: Some(false) }), document_highlight: Some(DynamicRegistrationClientCapabilities { dynamic_registration: Some(false) }), document_symbol: Some(DocumentSymbolClientCapabilities { dynamic_registration: Some(false), symbol_kind: Some(SymbolKindCapability { value_set: Some([File, Module, Namespace, Package, Class, Method, Property, Field, Constructor, Enum, Interface, Function, Variable, Constant, String, Number, Boolean, Array, Object, Key, Null, EnumMember, Struct, Event, Operator, TypeParameter]) }), hierarchical_document_symbol_support: Some(true), tag_support: Some(TagSupport { value_set: [Deprecated] }) }), formatting: Some(DynamicRegistrationClientCapabilities { dynamic_registration: Some(true) }), range_formatting: Some(DynamicRegistrationClientCapabilities { dynamic_registration: Some(true) }), on_type_formatting: None, declaration: Some(GotoCapability { dynamic_registration: None, link_support: Some(true) }), definition: Some(GotoCapability { dynamic_registration: Some(true), link_support: Some(true) }), type_definition: Some(GotoCapability { dynamic_registration: None, link_support: Some(true) }), implementation: Some(GotoCapability { dynamic_registration: None, link_support: Some(true) }), code_action: Some(CodeActionClientCapabilities { dynamic_registration: Some(true), code_action_literal_support: Some(CodeActionLiteralSupport { code_action_kind: CodeActionKindLiteralSupport { value_set: ["", "quickfix", "refactor", "refactor.extract", "refactor.inline", "refactor.rewrite", "source", "source.organizeImports"] } }), is_preferred_support: Some(true), disabled_support: Some(true), data_support: Some(true), resolve_support: Some(CodeActionCapabilityResolveSupport { properties: ["edit", "command"] }), honors_change_annotations: Some(true) }), code_lens: Some(DynamicRegistrationClientCapabilities { dynamic_registration: Some(false) }), document_link: None, color_provider: Some(DynamicRegistrationClientCapabilities { dynamic_registration: Some(true) }), rename: Some(RenameClientCapabilities { dynamic_registration: Some(true), prepare_support: Some(true), prepare_support_default_behavior: None, honors_change_annotations: Some(true) }), publish_diagnostics: Some(PublishDiagnosticsClientCapabilities { related_information: Some(true), tag_support: Some(TagSupport { value_set: [Unnecessary, Deprecated] }), version_support: None, code_description_support: None, data_support: Some(true) }), folding_range: Some(FoldingRangeClientCapabilities { dynamic_registration: Some(false), range_limit: None, line_folding_only: Some(true), folding_range_kind: Some(FoldingRangeKindCapability { value_set: Some([Comment, Imports, Region]) }), folding_range: Some(FoldingRangeCapability { collapsed_text: Some(true) }) }), selection_range: Some(SelectionRangeClientCapabilities { dynamic_registration: Some(false) }), linked_editing_range: Some(DynamicRegistrationClientCapabilities { dynamic_registration: Some(false) }), call_hierarchy: Some(DynamicRegistrationClientCapabilities { dynamic_registration: Some(false) }), semantic_tokens: Some(SemanticTokensClientCapabilities { dynamic_registration: Some(false), requests: SemanticTokensClientCapabilitiesRequests { range: Some(false), full: Some(Delta { delta: Some(true) }) }, token_types: [SemanticTokenType("namespace"), SemanticTokenType("type"), SemanticTokenType("class"), SemanticTokenType("enum"), SemanticTokenType("interface"), SemanticTokenType("struct"), SemanticTokenType("typeParameter"), SemanticTokenType("parameter"), SemanticTokenType("variable"), SemanticTokenType("property"), SemanticTokenType("enumMember"), SemanticTokenType("event"), SemanticTokenType("function"), SemanticTokenType("method"), SemanticTokenType("macro"), SemanticTokenType("keyword"), SemanticTokenType("modifier"), SemanticTokenType("comment"), SemanticTokenType("string"), SemanticTokenType("number"), SemanticTokenType("regexp"), SemanticTokenType("operator"), SemanticTokenType("decorator")], token_modifiers: [SemanticTokenModifier("declaration"), SemanticTokenModifier("definition"), SemanticTokenModifier("readonly"), SemanticTokenModifier("static"), SemanticTokenModifier("deprecated"), SemanticTokenModifier("abstract"), SemanticTokenModifier("async"), SemanticTokenModifier("modification"), SemanticTokenModifier("documentation"), SemanticTokenModifier("defaultLibrary")], formats: [TokenFormat("relative")], overlapping_token_support: Some(true), multiline_token_support: Some(true), server_cancel_support: Some(false), augments_syntax_tokens: Some(true) }), moniker: None, type_hierarchy: None, inline_value: None, inlay_hint: Some(InlayHintClientCapabilities { dynamic_registration: Some(true), resolve_support: Some(InlayHintResolveClientCapabilities { properties: ["textEdits", "tooltip", "location", "command"] }) }), diagnostic: Some(DiagnosticClientCapabilities { dynamic_registration: Some(false), related_document_support: Some(true) }) }), notebook_document: None, window: Some(WindowClientCapabilities { work_done_progress: Some(true), show_message: Some(ShowMessageRequestClientCapabilities { message_action_item: Some(MessageActionItemCapabilities { additional_properties_support: Some(true) }) }), show_document: Some(ShowDocumentClientCapabilities { support: true }) }), general: Some(GeneralClientCapabilities { regular_expressions: None, markdown: None, stale_request_support: None, position_encodings: Some([PositionEncodingKind("utf-8"), PositionEncodingKind("utf-16"), PositionEncodingKind("utf-32")]) }), experimental: None }, trace: Some(Off), workspace_folders: Some([WorkspaceFolder { uri: Uri(Uri { scheme: Some("file"), authority: Some(Authority { userinfo: None, host: Host { text: "", data: RegName("") }, port: None }), path: "/home/user/Downloads/test_asm_dir", query: None, fragment: None }), name: "/home/user/Downloads/test_asm_dir" }]), client_info: Some(ClientInfo { name: "Neovim", version: Some("0.12.0-dev+ga26cdcb20e") }), locale: None, work_done_progress_params: WorkDoneProgressParams { work_done_token: Some(String("1")) } }\nINFO [asm_lsp::lsp] Creating directories along /home/user/.config/asm-lsp as necessary...\nINFO [asm_lsp::lsp] Parsing global asm-lsp config from file -> /home/user/.config/asm-lsp/.asm-lsp.toml\nINFO [asm_lsp::lsp] Detected project root: /home/user/Downloads/test_asm_dir\nINFO [asm_lsp::lsp] Parsing asm-lsp project config from file -> /home/user/Downloads/test_asm_dir/.asm-lsp.toml\nINFO [asm_lsp::lsp] Detected project root: /home/user/Downloads/test_asm_dir\nINFO [asm_lsp::lsp] No `default_config` specified, filling in default options\nINFO [asm_lsp::types] Detected host arch as x86-64\nINFO [asm_lsp::types] Detected host arch as x86-64\nINFO [asm_lsp] Server Configuration: RootConfig { default_config: Some(Config { version: None, assembler: Gas, instruction_set: X86_64, opts: Some(ConfigOptions { compiler: None, compile_flags_txt: None, diagnostics: Some(true), default_diagnostics: Some(true) }) }), projects: Some([ProjectConfig { path: "/home/user/Downloads/test_asm_dir/src", config: Config { version: Some("0.10.0"), assembler: Gas, instruction_set: RISCV, opts: Some(ConfigOptions { compiler: Some("riscv64-unknown-elf-gcc"), compile_flags_txt: Some(["\\"-T riscv.ld\\"", "-nostdlib", "-march=rv32im_zicsr", "-mabi=ilp32"]), diagnostics: Some(true), default_diagnostics: Some(false) }) } }]) }\nINFO [asm_lsp::types] riscv instruction set loaded in 0ms\nINFO [asm_lsp::types] riscv register set loaded in 0ms\n'
[ERROR][2025-10-13 10:10:17] ...nvim-linux-x86_64/share/nvim/runtime/lua/vim/lsp/log.lua:151	"rpc"	"asm-lsp"	"stderr"	"INFO [asm_lsp::types] x86-64 instruction set loaded in 11ms\n"
[ERROR][2025-10-13 10:10:17] ...nvim-linux-x86_64/share/nvim/runtime/lua/vim/lsp/log.lua:151	"rpc"	"asm-lsp"	"stderr"	"INFO [asm_lsp::types] x86-64 register set loaded in 0ms\n"
[ERROR][2025-10-13 10:10:17] ...nvim-linux-x86_64/share/nvim/runtime/lua/vim/lsp/log.lua:151	"rpc"	"asm-lsp"	"stderr"	"INFO [asm_lsp::types] gas directive set loaded in 0ms\n"
[ERROR][2025-10-13 10:10:17] ...nvim-linux-x86_64/share/nvim/runtime/lua/vim/lsp/log.lua:151	"rpc"	"asm-lsp"	"stderr"	"INFO [asm_lsp::lsp] Detected project root: /home/user/Downloads/test_asm_dir\n"
[ERROR][2025-10-13 10:10:17] ...nvim-linux-x86_64/share/nvim/runtime/lua/vim/lsp/log.lua:151	"rpc"	"asm-lsp"	"stderr"	'INFO [asm_lsp::lsp] Include directory map: {All: ["/usr/include/c++/11/backward", "/usr/include/x86_64-linux-gnu/c++/11", "/usr/include", "/usr/lib/gcc/x86_64-linux-gnu/11/include", "/usr/local/include", "/usr/include/c++/11", "/usr/include/x86_64-linux-gnu"]}\nINFO [asm_lsp] Starting asm-lsp loop...\n'
[ERROR][2025-10-13 10:10:17] ...nvim-linux-x86_64/share/nvim/runtime/lua/vim/lsp/log.lua:151	"rpc"	"asm-lsp"	"stderr"	"INFO [asm_lsp::handle] textDocument/didOpen notification serviced in 0ms\n"
[ERROR][2025-10-13 10:10:17] ...nvim-linux-x86_64/share/nvim/runtime/lua/vim/lsp/log.lua:151	"rpc"	"asm-lsp"	"stderr"	'INFO [asm_lsp::types] Selected project config with path "/home/user/Downloads/test_asm_dir/src"\nINFO [asm_lsp::types] Selected project config with path "/home/user/Downloads/test_asm_dir/src"\nINFO [asm_lsp::handle] Selected compile command(s) for request: [CompileCommand { directory: "", file: File("/home/user/Downloads/test_asm_dir/src/main.S"), arguments: Some(Arguments(["riscv64-unknown-elf-gcc", "\\"-T riscv.ld\\"", "-nostdlib", "-march=rv32im_zicsr", "-mabi=ilp32", "/home/user/Downloads/test_asm_dir/src/main.S"])), command: None, output: None }]\nINFO [asm_lsp::lsp] Attempting to apply compile command: CompileCommand { directory: "", file: File("/home/user/Downloads/test_asm_dir/src/main.S"), arguments: Some(Arguments(["riscv64-unknown-elf-gcc", "\\"-T riscv.ld\\"", "-nostdlib", "-march=rv32im_zicsr", "-mabi=ilp32", "/home/user/Downloads/test_asm_dir/src/main.S"])), command: None, output: None }\n'
[ERROR][2025-10-13 10:10:17] ...nvim-linux-x86_64/share/nvim/runtime/lua/vim/lsp/log.lua:151	"rpc"	"asm-lsp"	"stderr"	"INFO [asm_lsp::handle] textDocument/diagnostic request serviced in 30ms\n"

If they're still showing up in the wrong spot, could you provide the output from invoking your compiler on the source file manually? The server provides diagnostics by invoking the compiler and parsing its output, its possible the source location for an error isn't being gathered correctly.

This seems like a .include directive specific thing on my end. For reference make build --dry-run:

rm -rf build *.o
mkdir -p build
riscv64-unknown-elf-as -march=rv32im_zicsr -mabi=ilp32 -I src -o build/main.o src/main.S
mkdir -p build
riscv64-unknown-elf-as -march=rv32im_zicsr -mabi=ilp32 -I src -o build/regs.o src/regs.S
mkdir -p build
riscv64-unknown-elf-as -march=rv32im_zicsr -mabi=ilp32 -I src -o build/startup.o src/startup.S
mkdir -p build
riscv64-unknown-elf-as -march=rv32im_zicsr -mabi=ilp32 -I src -o build/syscalls.o src/syscalls.
S
mkdir -p build
riscv64-unknown-elf-as -march=rv32im_zicsr -mabi=ilp32 -I src -o build/trap.o src/trap.S
riscv64-unknown-elf-gcc -nostdlib -T src/riscv.ld -march=rv32im_zicsr -mabi=ilp32 -o build/main
 build/lib.o build/macro.o build/main.o build/regs.o build/startup.o build/syscalls.o build/tra
p.o
riscv64-unknown-elf-objdump  -M no-aliases -dtSr build/main > build/main.dis

[WillLillis]

Sorry it took me so long to get back to this!

The lsp errors are gone, but now it just display No information available for the pseudo-commands and ABI register names.

That is unfortunately the expected behavior currently, as the source we use for RISC-V documentation isn't comprehensive. There are some vague plans to improve this (see #165), but I haven't checked in on the project in a bit.

For the labels starting with having format .LABEL_NAME gd displays No locations found. But for label names not starting with . it works as intended.

Ah, there may be an easy fix to this problem at least, I'll try to look into this soon.

I seems it does not work with labels resolved in another file.

This is a known limitation of the server currently. It's a problem I'd like to resolve at some point, but it will be a bit messy and will have to be handled on an assembler-by-assembler basis.

Could you elaborate on the what tree-sitter considers a valid goto definition and what it doesn't?

The server uses tree-sitter-asm, which takes in a source file and produces a concrete syntax tree (CST). We can then query this CST for various items of interest (i.e. registers, labels, instructions, etc.). but it only works on one file at a time. tree-sitter-asm is intended to be a general purpose assembly grammar to provide highlighting for various architectures, assemblers, etc. Because of this, it mis-parses in plenty of edge cases. If you're curious about how tree-sitter-asm is parsing your source files, I'd be happy to give you some more specific tips here :)

Yes, the same errors appear when I run the mentioned commands in compile_commands.json. I am using make run to build the project. It basically converts the .S files into .o files in build/ folder, then it further runs a command which links these object files together to produce the executable.

Probably need to generate the compile_commands.json using the makefile, but that is proving a little more challenging than I had thought and does not fit the scope of this discussion. (If someone wants to explore why, I am trying to use bear and am unable to resolve the path for the executable. This rizsotto/Bear#642 explains the issue but is for another compiler suite)

Ah, that makes sense. I don't think there's a great solution for asm-lsp here directly, but I can take a look. Regardless of your issues here, the server's diagnostics logic definitely needs a rework 😆. Maybe the server could just run a command (i.e. make build in your case) and parse the diagnostics from that command's output?

[irtaza-10x]

Yea I believe that would work. Thanks for the tip! If I get some time I will try to fix the bear logic and stuff.

[WillLillis]

@tbung

The asm_lsp: -32803: No information available message is harmless and can be ignored. If that's being displayed prominently (I haven't seen that locally, but it may be config-dependent), I can look into a fix.

Regarding the other error in your message, this appears to be an issue with your neovim configuration:

		if (
                vim.tbl_contains(client.server_capabilities.signatureHelpProvider.triggerCharacters, current_char, {})
                or (
                  client.server_capabilities.signatureHelpProvider.retriggerCharacters
                  and vim.tbl_contains(client.server_capabilities.signatureHelpProvider.retriggerCharacters, current_char, {})
                )
              ) then
            require("tillb.signature").signature_help()
          end

The error indicates that client.server_capabilities.signatureHelpProvider is nil. I'm not sure why, since asm-lsp does support textDocument/signatureHelp with some trigger characters. Can you do some investigating locally to see what's causing this? I don't think there's anything I can do for this currently.

[tbung]

Oh, thanks for catching that, the big error is indeed that client.server_capabilities.signatureHelpProvider.triggerCharacters is nil, sinatureHelpProvider only contains workDoneProgress = false. Seems like trigger characters are not actually in the server capabilities.

asm-lsp/asm-lsp/bin/main.rs

Lines 128 to 130 in 9df3f51

	let signature_help_provider = Some(SignatureHelpOptions {
	trigger_characters: None,
	retrigger_characters: None,

Definitely my bad for not catching that myself, sorry! I'm not sure how important that is to add that, I personally don't really need signature help for asm, but since the lsp does support it it might make sense to provide trigger chars.

asm_lsp: -32803: No information available is way less of an issue, it is displayed somewhat prominently but doesn't get in the way, and it definitely is show because of my own janky notify implementation, so don't worry about that.