This is the mail archive of the
mailing list for the elfutils project.
Re: RISC-V support
- From: Mark Wielaard <mark at klomp dot org>
- To: Kurt Roeckx <kurt at roeckx dot be>
- Cc: Jim Wilson <jimw at sifive dot com>, elfutils-devel at sourceware dot org, Karsten Merker <merker at debian dot org>
- Date: Sat, 12 Jan 2019 23:35:48 +0100
- Subject: Re: RISC-V support
- References: <CAFyWVaa3aixXz2zUN_aBSC9=CpkOXNPxCiun1MP-htghRqqwuw@mail.gmail.com> <email@example.com> <20190111232332.GA12090@roeckx.be>
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:
> mips_return_value_location (Dwarf_Die *functypedie, const Dwarf_Op
> /* First find the ABI used by the elf object */
> enum mips_abi abi = find_mips_abi(functypedie->cu->dbg->elf);
> The patch only supports 6 ABIs, but I think there are really over
> 10 ABIs.
But how many are actually used? Which does Debian support?
> Maybe it would be good that we only need to determine the ABI
> once, instead of each time the function is called.
Yes, so instead of having each hook find the correct abi, you can do
that in the init hook once. And then either assigning a abi specific
callback hook, or setting some struct ebl data field (ppc64 added one
for function descriptor support for example).