On Mon, 01 May 2017 03:54:49 PDT (-0700), jos...@codesourcery.com wrote:
> On Mon, 1 May 2017, Palmer Dabbelt wrote:
>
>> > Specifically, in such cases the GCC configure option is
>> > --enable-target=all to enable 64-bit multilibs for a default-32-bit
>> > target, and the binutils/GDB configure op
On Mon, 1 May 2017, Palmer Dabbelt wrote:
> > Specifically, in such cases the GCC configure option is
> > --enable-target=all to enable 64-bit multilibs for a default-32-bit
> > target, and the binutils/GDB configure option is --enable-64-bit-bfd. But
> > you can also make a binutils/GDB target i
On Sun, 30 Apr 2017 16:38:35 PDT (-0700), jos...@codesourcery.com wrote:
> On Sat, 29 Apr 2017, Richard Biener wrote:
>> On April 29, 2017 3:59:27 AM GMT+02:00, Palmer Dabbelt
>> wrote:
>> >We've been telling people that "riscv32-*" and "riscv64-*" are exactly
>> >the same toolchain aside from de
On Sat, 29 Apr 2017, Richard Biener wrote:
> On April 29, 2017 3:59:27 AM GMT+02:00, Palmer Dabbelt
> wrote:
> >We've been telling people that "riscv32-*" and "riscv64-*" are exactly
> >the same toolchain aside from defaults for "-march" and "-mabi", but it
> >appears we were lying. As far as I
On April 29, 2017 3:59:27 AM GMT+02:00, Palmer Dabbelt
wrote:
>We've been telling people that "riscv32-*" and "riscv64-*" are exactly
>the same toolchain aside from defaults for "-march" and "-mabi", but it
>appears we were lying. As far as I can tell, binutils doesn't support
>64-bit targets wh
We've been telling people that "riscv32-*" and "riscv64-*" are exactly
the same toolchain aside from defaults for "-march" and "-mabi", but it
appears we were lying. As far as I can tell, binutils doesn't support
64-bit targets when it has been configured for a 32-bit target. This
seems to be an
