You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm requesting support for LoongArch, a RISC-based instruction set architecture developed by Loongson.
Having recently ported VSCodium to LoongArch, I noticed that the Open VSX Registry offers very limited options for C/C++ and Rust debuggers. And none of them offers support for the architecture.
I would like to request native .vsix builds for LoongArch support. I'm also willing to contribute by helping with the CI pipeline updates.
The text was updated successfully, but these errors were encountered:
Building Codelldb itself for another arch is not the problem, building LLDB with Python support is. Right now I'm using binaries from Python Standalone to get portable Python. As you can see, they don't provide builds for LoongArch.
Another issue is that I don't have the hardware to test or debug on. And neither does Azure (which is used for CI).
If your distro's repository provides LLVM 18 or later, I'd recommend trying LLDB's own DAP adapter.
Thank you for the detailed explanation. Regarding the issues you mentioned:
For Python Standalone support, I'll look into adding LoongArch support.
As for the hardware limitation, would it be feasible to test the implementation using QEMU emulation?
About LLDB DAP - while it's definitely a promising solution, I noticed it's not yet available on Open VSX (the default marketplace for VSCodium). There's an ongoing discussion about this at llvm/llvm-project#93544, and I am going to see if any progress could be made.
I'm requesting support for LoongArch, a RISC-based instruction set architecture developed by Loongson.
Having recently ported VSCodium to LoongArch, I noticed that the Open VSX Registry offers very limited options for C/C++ and Rust debuggers. And none of them offers support for the architecture.
I would like to request native
.vsix
builds for LoongArch support. I'm also willing to contribute by helping with the CI pipeline updates.The text was updated successfully, but these errors were encountered: