[riot-notifications] [RIOT-OS/RIOT] fe310: Support compilation with clang (#15176)
notifications at github.com
Fri Nov 6 09:32:34 CET 2020
> Just to make sure I understand your proposal correctly: You would go ahead and change the default compiler triplet in the RIOT RISC-V Makefile, in the RIOT Docker image, and possible also in the Alpine Linux package to `riscv32-none-elf`?
No, I don't think that makes sense for GCC. Who would assume that a `riscv32-none-elf-gcc` would be capable of building both 32 and 64 bit binaries?
I mean, if you have separate packages for RISC-V 32bit and 64 bit it would totally make sense to have `riscv32-none-elf` for the 32 bit, and `riscv64-none-elf` for the other. But a GCC capable of both is IMO best named `riscv-none-elf`.
What I meant with:
> This doesn't need to be configurable for clang, riscv32-none-elf will work with version of clang.
Just use `riscv32-none-elf` as triple for `clang`, regardless of what RISC-V GCC toolchain is installed. This is especially beneficial if no GCC toolchain is installed.
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the notifications