Re: RISC-V support

2019-01-13 Thread Jim Wilson
On Sat, Jan 12, 2019 at 5:23 PM Kurt Roeckx wrote: > O32 really has at least the following variants: > - O32 FP32 > - O32 FPXX > - O32 FP64 > - O32 FP64A The FPXX and FP64A stuff is new, after I stopped tracking MIPS stuff, so I hadn't noticed it. I see why they added these, but if you count sof

Re: RISC-V support

2019-01-12 Thread Kurt Roeckx
On Sat, Jan 12, 2019 at 05:06:18PM -0800, Jim Wilson wrote: > On Sat, Jan 12, 2019 at 3:21 PM Kurt Roeckx wrote: > > > But how many are actually used? Which does Debian support? > > > > I'm not at all an export of mips, I really don't know that much > > about it. > > It depends on how you count A

Re: RISC-V support

2019-01-12 Thread Jim Wilson
On Sat, Jan 12, 2019 at 3:21 PM Kurt Roeckx wrote: > > But how many are actually used? Which does Debian support? > > I'm not at all an export of mips, I really don't know that much > about it. It depends on how you count ABIs, but yes there have unfortunately been a lot of them over the years.

Re: RISC-V support

2019-01-12 Thread Kurt Roeckx
On Sat, Jan 12, 2019 at 11:35:48PM +0100, Mark Wielaard wrote: > On Sat, 2019-01-12 at 00:23 +0100, Kurt Roeckx wrote: > > I've been looking at mips, and it seems to have many different > > ABIs too. A patch I've received does this: > > int > > mips_return_value_location (Dwarf_Die *functypedie, co

Re: RISC-V support

2019-01-12 Thread Mark Wielaard
On Sat, 2019-01-12 at 00:23 +0100, Kurt Roeckx wrote: > I've been looking at mips, and it seems to have many different > ABIs too. A patch I've received does this: > int > mips_return_value_location (Dwarf_Die *functypedie, const Dwarf_Op > **locp) > { > /* First find the ABI used by the elf obje

Re: RISC-V support

2019-01-11 Thread Kurt Roeckx
On Tue, Jan 08, 2019 at 02:52:33PM +0100, Mark Wielaard wrote: > > There is a problem here though. The riscv support was written to try > > to handle both 32-bit and 64-bit targets with a single elfutils > > backend. But I have 6 ABIs I need to (theoretically) handle in > > riscv_retval.c. The r

Re: RISC-V support

2019-01-08 Thread Jim Wilson
On Tue, Jan 8, 2019 at 5:52 AM Mark Wielaard wrote: > The _start one seems to be: > https://sourceware.org/bugzilla/show_bug.cgi?id=23125 > So that is fixed with glibc 2.29. > > Do you have a bug for the second issue with __thread_start? https://sourceware.org/bugzilla/show_bug.cgi?id=24040 I pl

Re: RISC-V support

2019-01-08 Thread Mark Wielaard
Hi Jim, Apologies for the late reply, holiday season. Seeing some patches already posted I think you already found the answers to your questions, but just to be sure, lets answer this email before reviewing the actual patches. On Wed, 2018-12-26 at 18:29 -0800, Jim Wilson wrote: > I'm looking at

RISC-V support

2018-12-26 Thread Jim Wilson
I'm looking at the RISC-V elfutils support to help the Debian folks. I see four testcases failing, same as Kurt Roeckx reported about 6 weeks ago. I'm testing on a Fedora Core 29 system. I found a trivial bug in backends/riscv_corenote.c. It has ".offset = 1" but this is a byte offset not a regi