Yan Titarenko

And what about https://github.com/aguinet/dragonffi ?

@palmer-dabbelt , ping on you

I wonder if there is any demand on an interop scenario, against LLVM's IR. Something like Python->IR and Golang->IR compilation, which could be passed to specific back-end. Duplicating my question:...

Threw a modification of https://github.com/facebookincubator/fbender/blob/master/.circleci/config.yml ?

There is a problem: since that's another Golang's installation distribution - it would raise a conflict with a pre-installed Go. How could I configure a "clean" environment setup?

@earlgreyz , consider investigating https://github.com/advancedwebdeveloper/clang_test_cpu_features/actions/runs/405495534 https://github.com/advancedwebdeveloper/clang_test_cpu_features/blob/main/.github/workflows/llvm.yml

> ~/Desktop/rust-sipeed-longan-nano-master$ cargo build > Compiling r0 v0.2.2 > Compiling panic-abort v0.3.1 > Compiling rust-sipeed-longan-nano v0.1.0 (/home/oceanfish81/Desktop/rust-sipeed-longan-nano-master) > warning: unnecessary parentheses around assigned value > --> src/main.rs:8:25 > | >...

That's with > [target.riscv32imac-unknown-none-elf] > linker = "riscv32-unknown-elf-gcc"

However with > [target.riscv32imac-unknown-none-elf] > linker = "riscv32-unknown-elf-ld" I didn't get any error: > $ cargo build > Compiling panic-abort v0.3.1 > Compiling r0 v0.2.2 > Compiling rust-sipeed-longan-nano v0.1.0 (/home/oceanfish81/Desktop/rust-sipeed-longan-nano-master)...

I am able to see the binary file, as described [here](https://pramode.in/2019/10/07/rust-on-riscv-board-sipeed-longan-nano/) - it is just I have my toolchain offers "riscv32-unknown-elf" prefix, for the executibles, instead of "riscv-nuclei-elf-"