From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14087 invoked by alias); 12 Jan 2019 22:35:52 -0000 Mailing-List: contact elfutils-devel-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Post: List-Help: List-Subscribe: Sender: elfutils-devel-owner@sourceware.org Received: (qmail 14020 invoked by uid 89); 12 Jan 2019 22:35:51 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Checked: by ClamAV 0.100.2 on sourceware.org X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_PASS autolearn=ham version=3.3.2 spammy=Which X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_PASS autolearn=ham version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on sourceware.org X-Spam-Level: X-HELO: gnu.wildebeest.org Received: from wildebeest.demon.nl (HELO gnu.wildebeest.org) (212.238.236.112) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sat, 12 Jan 2019 22:35:50 +0000 Received: from tarox.wildebeest.org (tarox.wildebeest.org [172.31.17.39]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by gnu.wildebeest.org (Postfix) with ESMTPSA id 3B7113000AF4; Sat, 12 Jan 2019 23:35:48 +0100 (CET) Received: by tarox.wildebeest.org (Postfix, from userid 1000) id 29EC9413CA13; Sat, 12 Jan 2019 23:35:48 +0100 (CET) Message-ID: Subject: Re: RISC-V support From: Mark Wielaard To: Kurt Roeckx Cc: Jim Wilson , elfutils-devel@sourceware.org, Karsten Merker Date: Sat, 12 Jan 2019 22:35:00 -0000 In-Reply-To: <20190111232332.GA12090@roeckx.be> References: <20190111232332.GA12090@roeckx.be> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Evolution 3.28.5 (3.28.5-2.el7) Mime-Version: 1.0 X-Spam-Flag: NO X-IsSubscribed: yes X-SW-Source: 2019-q1/txt/msg00029.txt.bz2 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 object */ > enum mips_abi abi =3D find_mips_abi(functypedie->cu->dbg->elf); >=20 > 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). Cheers, Mark