[Lldb-commits] [lldb] [llvm] [lldb] Extended if conditions to support alias names for registers (PR #124475)

[David Spickett via lldb-commits]

DavidSpickett wrote:

> I have added a live process test. But I struggle to test it (it is currently wrong on purpose - so ignore a eventually green pipeline). First off, I struggle to build libc with RISCV (I am cross compiling from x86-64). Additionally, I will probably have problems running the (riscv) test from my host system.

Not sure why you need the libc. You can use a pre-compiled gcc based toolchain for RISC-V (wherever one gets those, Arm provides such things for Arm I know that).

> Additionally, I will probably have problems running the (riscv) test from my host system.
> Is there any documentation how to build and test it?

There are - and I merged more of them just today in fact.

For that you will need host tools, and lldb-server for the remote RISC-V machine. The way I do this for Arm is I have a totally vanilla host build, then https://lldb.llvm.org/resources/build.html#example-1-cross-compiling-for-linux-arm64-on-ubuntu-host for the cross build. That build only needs lldb-server (`ninja lldb-server`).

scp that lldb-server to the RISC-V board, then follow https://lldb.llvm.org/resources/test.html#running-the-test-suite-remotely

I suggest at first you stick to using `dotest` because you'll be running single tests anyway. Then you can try to get `ninja check-lldb` working if you like, but I expect RISC-V to have a lot of failures. If you really want to, just compare it against a baseline to see that your changes don't break anything else.

You'll be running those `dotest` commands in the *host* build folder, because you want to run the host version of lldb, connecting to the remote RISC-V board.

For some more inspiration we do have a few remote debug bots - https://lab.llvm.org/buildbot/#/builders/195/builds/4388/steps/6/logs/stdio - this one does Linux something (x86?) to Linux AArch64.

Also, you can use clang as the LLDB_TEST_COMPILER, but if you've got a cross toolchain for RSIC-V anyway, I'd just point it to that. In my case that's usually `aarch64-linux-gcc`.

> Is it possible to schedule like a CI job?

Generally, no. There's no way to request an existing buildbot run a pre-commit branch. One day maybe. It's quite a popular request.

Specifically, no, because there's no RISC-V LLDB testing in the buildbot system. One can only hope RISC-V enthusiasts address this eventually (folks are putting up qmu-system powered bots, so in theory it's not that far off).

https://github.com/llvm/llvm-project/pull/124475