This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] RISC-V: Don't built 64-bit multilibs on 32-bit targets
- From: Palmer Dabbelt <palmer at dabbelt dot com>
- To: joseph at codesourcery dot com
- Cc: richard dot guenther at gmail dot com
- Cc: gcc-patches at gcc dot gnu dot org
- Cc: patches at groups dot riscv dot org
- Date: Mon, 01 May 2017 13:41:24 -0700 (PDT)
- Subject: Re: [PATCH] RISC-V: Don't built 64-bit multilibs on 32-bit targets
- Authentication-results: sourceware.org; auth=none
On Mon, 01 May 2017 03:54:49 PDT (-0700), joseph@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 option is --enable-64-bit-bfd. But
>> > you can also make a binutils/GDB target include 64-bit support
>> > unconditionally without requiring --enable-64-bit-bfd.
>>
>> Do you happen to know how to do that (enable 64-bit BFDs in a 32-bit binutils
>> build)? I'd prefer to have the riscv32 and riscv64 ports the same if possible,
>> but poked around a bit and couldn't find a way to do it.
>
> Well, certainly you should add riscv_elf64_vec to targ_selvecs in
> config.bfd for the riscv32-*-* case. Generally, check all the configure
> fragments used for riscv* to make sure they include both 32-bit and 64-bit
> support.
Thanks, I think that was all I was missing. I've submitted a binutils patch,
so let's consider this matter closed in GCC land.