[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH] Add "riscv" as an alias for "riscv32"
From: |
DJ Delorie |
Subject: |
Re: [PATCH] Add "riscv" as an alias for "riscv32" |
Date: |
Thu, 21 Jun 2018 21:17:45 -0400 |
If by this patch you mean that "riscv-unknown-linux-gnu" means EITHER
riscv32 (when on a 32-bit os) OR riscv64 (when on a 64-bit os), then I
would prefer *against* this, as it would mean that config.guess would
return an ambigious value - there is no version of GNU/Linux that
supports both riscv32 and riscv64 at the same time.
Keeping the 32/64 suffix is consistent with the s390/s390x case right
below it, where s390 is 31-bit and s390x is 63-bit, rather than having
one name mean "either".
We also don't combine x86_64 and i*86, and *one* chips supports both of
those.
I have no problem with users selecting riscv-* explicitly, or toolchains
shortening prefixes. TPF does this (resulting programs are like
tpf-gcc, not tpf-something-else-gcc) for example. But that shouldn't be
config.guess's job. Config.guess is used for more than the toolchain's
default program name.
Re: [PATCH] Add "riscv" as an alias for "riscv32", Ben Elliston, 2018/06/21
Re: [PATCH] Add "riscv" as an alias for "riscv32", Richard W.M. Jones, 2018/06/22
Re: [PATCH] Add "riscv" as an alias for "riscv32", Palmer Dabbelt, 2018/06/22
Message not availableRe: [PATCH] Add "riscv" as an alias for "riscv32", John Ericson, 2018/06/22