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 3 Jul 2018, at 20:41, Jim Wilson 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 p
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
> On 3 Jul 2018, at 13:29, Ben Elliston wrote:
>
> OK, how about this? This patch makes everything uniform
for my embedded toolchain it seems ok.
however please note that I did not try to update my `riscv-none-embed-` build
scripts to use this new structure; actually my scripts are still ba
OK, how about this? This patch makes everything uniform (see test
cases below for an illustration of behaviour):
diff --git a/config.sub b/config.sub
index 072700f..c95acc6 100755
--- a/config.sub
+++ b/config.sub
@@ -625,7 +625,7 @@ case $basic_machine in
| powerpc | powerpc64 | powerpc64
