[riot-notifications] [RIOT-OS/RIOT] fe310: Support compilation with clang (#15176)

Marian Buschsieweke notifications at github.com
Thu Nov 5 19:55:53 CET 2020

@nmeum: I can also reproduce the issue. I don't think there is a need to have the GCC target triple and the clang target triple identical, e.g. the legacy toolchain with `riscv-none-embed` might still be used and that triple is not going to get support from clang.

However: I suggest to use `riscv32-none-elf` over `riscv32-unknown-elf`, as IMO `unknown` is just obfuscating what is actually used.

The reason that for GCC I chose `riscv-none-elf` over `riscv32-none-elf` is that the triplet is there not used as parameter, but part of the file name. And that toolchain is compiled with multilib support and can emit code for both 32 bit and 64 bit flavors of RISC-V, so I figured `riscv` is less misleading than `riscv32` or `riscv64` there.

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...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20201105/bdaae3b0/attachment.htm>

More information about the notifications mailing list