On Mon, Jul 09, 2018 at 08:41:09AM -0700, Jim Wilson wrote:
> 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
On Mon, Jul 9, 2018 at 4:07 AM, Liviu Ionescu wrote:
>> On 9 Jul 2018, at 12:20, Ben Elliston 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
> On 9 Jul 2018, at 12:20, Ben Elliston 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.
>
>> There are no plans for any t
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.
> There are no plans for any tools to accept riscv- as a CPU, so
> adding support for this to
