From: Kurt Roeckx <kurt@roeckx.be>
To: Mark Wielaard <mark@klomp.org>
Cc: Jim Wilson <jimw@sifive.com>,
elfutils-devel@sourceware.org, Karsten Merker <merker@debian.org>
Subject: Re: RISC-V support
Date: Sat, 12 Jan 2019 23:21:00 -0000 [thread overview]
Message-ID: <20190112232136.GA32419@roeckx.be> (raw)
In-Reply-To: <dab3d9df5b578155bfc7c20067576ba6e3b65164.camel@klomp.org>
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, const Dwarf_Op
> > **locp)
> > {
> > /* 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?
I'm not at all an export of mips, I really don't know that much
about it.
We have 3 mips ports, but mips and mipsel are the same ABI, it's
just big endian vs little endian. But as far as I understand it,
we transitioned those 2 ports from one ABI to an other, so they
are compatible with yet an other ABI. I think that at least makes
4 ABIs we care about. And I think gcc supports many different ones
depending on compiler flags you give to it, but I really don't know.
Kurt
next prev parent reply other threads:[~2019-01-12 23:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-27 2:29 Jim Wilson
2019-01-08 13:52 ` Mark Wielaard
2019-01-08 19:28 ` Jim Wilson
2019-01-08 21:52 ` Karsten Merker
2019-01-11 23:23 ` Kurt Roeckx
2019-01-12 22:35 ` Mark Wielaard
2019-01-12 23:21 ` Kurt Roeckx [this message]
2019-01-13 1:06 ` Jim Wilson
2019-01-13 1:23 ` Kurt Roeckx
2019-01-13 22:15 ` Jim Wilson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190112232136.GA32419@roeckx.be \
--to=kurt@roeckx.be \
--cc=elfutils-devel@sourceware.org \
--cc=jimw@sifive.com \
--cc=mark@klomp.org \
--cc=merker@debian.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).