On Mon, Jul 9, 2018 at 4:07 AM, Liviu Ionescu <i...@livius.net> wrote: >> On 9 Jul 2018, at 12:20, Ben Elliston <b...@air.net.au> wrote: >> >> On Tue, Jul 03, 2018 at 10:41:49AM -0700, Jim Wilson wrote: >> >>> Accepting riscv-linux isn't OK. That will cause complications. >>> Though I'm not sure if that can be easily avoided if we allow >>> riscv-elf.
We already merged config.sub patches into binutils and gcc, and added riscv-* support to them. So at this point I think we just have to allow riscv-*-* even though we don't want it. I don't expect to use it and I don't expect to maintain it, but some stubborn people will never give up on it, so we have to allow it. I don't care about Liviu, but there is a riscv-rtems port rolling out. We had agreement to expand riscv-rtems to riscv32-rtems at config.sub time, but then you modified config.sub to remove the riscv->riscv32 conversion, so the riscv-rtems port went out as just riscv-rtems and we can't drop support for that now. Jim _______________________________________________ config-patches mailing list config-patches@gnu.org https://lists.gnu.org/mailman/listinfo/config-patches
