This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH 5/5] RISC-V: Add configure support riscv*-linux*.
- From: Tom Tromey <tom at tromey dot com>
- To: Palmer Dabbelt <palmer at sifive dot com>
- Cc: tom at tromey dot com, Jim Wilson <jimw at sifive dot com>, gdb-patches at sourceware dot org
- Date: Wed, 08 Aug 2018 17:25:59 -0600
- Subject: Re: [PATCH 5/5] RISC-V: Add configure support riscv*-linux*.
- References: <mhng-434a3c5a-e632-4132-8fbf-bca82f51a81c@palmer-si-x1c4>
>>>>> "Palmer" == Palmer Dabbelt <palmer@sifive.com> writes:
Palmer> To enable this support in BFD we decided to put both the 32-bit and 64-bit
Palmer> RISC-V targets in the list of 32-bit targets. This allows toolchains
Palmer> configured with the 32-bit tuples to generate code for the 64-bit targets,
Palmer> which when coupled with multilib gives you a functioning setup.
Palmer> I'd like to keep this behavior in GDB if possible, so "riscv32-unknown-elf-gdb"
Palmer> can debug rv64i-based targets.
My main concern is really whether --disable-64-bit-bfd still works.
I don't know if people still use this, but as long as it exists it seems
like it should continue to work. If RISC-V works in this setup, then it
is totally fine by me for gdb to follow, assuming it works as well.
Maybe to really test it has to be a 32 bit build with
--disable-64-bit-bfd and --enable-targets=all.
Tom