On Tue, Jul 3, 2018 at 10:54 AM, Liviu Ionescu <i...@livius.net> wrote: >> I think Liviu's argument has a flaw. While it is true that both riscv32 and >> risvc64 can emit both 32-bit and 64-bit code, they have different defaults. >> riscv32 emits 32-bit by default, and riscv64 emits 64-bit by default. That >> is a property we lose if we allow riscv, because it won't be obvious if >> 32-bit or 64-bit code is the default. > > The defaults you mention apply to the Linux compilers, which are not the > topic of this thread.
Ben's latest patch suggestion adds riscv-linux support, which makes linux concerns relevant to this thread. > To minimise uncertainty, the embedded cross compilers should not provide such > defaults, the `-march` option should be mandatory, preferably the `-mabi` > option too. This would break the embedded cross compilers for most people. I don't think it would be wise to do this. I'm not aware of any other GNU toolchain that works this way. There is always a default architecture and ABI. Jim _______________________________________________ config-patches mailing list config-patches@gnu.org https://lists.gnu.org/mailman/listinfo/config-patches
