From: Jim Wilson <jimw@sifive.com>
To: Kurt Roeckx <kurt@roeckx.be>
Cc: Mark Wielaard <mark@klomp.org>,
elfutils-devel@sourceware.org,
Karsten Merker <merker@debian.org>
Subject: Re: RISC-V support
Date: Sun, 13 Jan 2019 22:15:00 -0000 [thread overview]
Message-ID: <CAFyWVaZRN01c2NBT_Eo2nXpoS_X0sryKbfKkGtbLXbdUXx_bCw@mail.gmail.com> (raw)
In-Reply-To: <20190113012334.GB22641@roeckx.be>
On Sat, Jan 12, 2019 at 5:23 PM Kurt Roeckx <kurt@roeckx.be> 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
soft-float, single-float, no-float, and a now deprecated 64-bit FP reg
mode, there are 8 different ways to handle FP code for o32. Crazy.
Most of them aren't relevant to linux though. And I suppose 20-30
years from now RISC-V may have the same problem.
Jim
prev parent reply other threads:[~2019-01-13 22:15 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
2019-01-13 1:06 ` Jim Wilson
2019-01-13 1:23 ` Kurt Roeckx
2019-01-13 22:15 ` Jim Wilson [this message]
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=CAFyWVaZRN01c2NBT_Eo2nXpoS_X0sryKbfKkGtbLXbdUXx_bCw@mail.gmail.com \
--to=jimw@sifive.com \
--cc=elfutils-devel@sourceware.org \
--cc=kurt@roeckx.be \
--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).