On 4/17/19 2:21 AM, chunmin.c...@sifive.com wrote:
cd scripts/elf2hex/build/; \
/c/Users/chunmin.chen/wsFreedomStudio/e34/scripts/elf2hex/configure \
--prefix=/c/Users/chunmin.chen/wsFreedomStudio/e34/scripts/elf2hex/install
\
--target=riscv64-unknown-elf
/c/Users/chunmin.chen
On Mon, Jul 9, 2018 at 10:15 PM, Ben Elliston wrote:
> OK--I don't terribly mind what is done as long as it is clear and
> uniform. If you think riscv/riscv-* should be allowed, I am happy to
> put it back.
Yes, please put it back, as riscv-rtems is using it.
Jim
__
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.
>>> Thoug
On Tue, Jul 3, 2018 at 10:54 AM, Liviu Ionescu 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
>>
On 07/03/2018 03:29 AM, Ben Elliston wrote:
+riscv-linuxriscv-unknown-linux-gnu
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 ac
