From: Richard Henderson <rth@twiddle.net>
To: Alexander Graf <agraf@suse.de>, Tom Musta <tommusta@gmail.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
"qemu-ppc@nongnu.org" <qemu-ppc@nongnu.org>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [Qemu-ppc] PowerPC Decimal Floating Point
Date: Fri, 14 Feb 2014 13:22:48 -0800 [thread overview]
Message-ID: <52FE8928.300@twiddle.net> (raw)
In-Reply-To: <767F99CE-BBF8-4682-969C-CE77389024AF@suse.de>
On 02/11/2014 11:38 PM, Alexander Graf wrote:
>> > My proposal is to incorporate the libdecnumber component of libdfp
>> > (http://www.eglibc.org/cgi-bin/viewvc.cgi/libdfp/trunk/) in a manner analogous to how
>> > softfloat is used for binary floating point. So, for example, the helper for the dadd
>> > instruction would look something like the following:
>> >
>> > - map FPSCR state to a decContext.
>> > - convert the contents of the source FPRs to decNumbers (decimal64ToNumber).
>> > - call decNumberAdd
>> > - convert the resultant decNumber to DPD (decimal64FromNumber)
>> > - update FPSCR per the decContext.status and result.
>> >
>> > Comments?
> I think that approach makes a lot of sense, but let's ask Richard and Peter as well.
Reasonable, as far as the implementation details go.
I am a teeny bit concerned which version of libdecnumber is considered most
"upstream". Ordinarily I'd point to the copy in gcc, but that is of course
GPLv3 + GCC runtime exception. I see the version from eglibc you quote above
is LGPLv2.1. I also see that the last change is 18 months old. On the other
hand, there is only one non-autoconf change in the gcc sources in the same period.
The original import is from IBM sources. Is there somewhere "upstream" at IBM
that we ought to be importing from instead?
r~
next prev parent reply other threads:[~2014-02-14 21:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-11 17:14 [Qemu-devel] PowerPC Decimal Floating Point Tom Musta
2014-02-12 7:38 ` [Qemu-devel] [Qemu-ppc] " Alexander Graf
2014-02-14 21:22 ` Richard Henderson [this message]
2014-02-14 22:22 ` Tom Musta
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=52FE8928.300@twiddle.net \
--to=rth@twiddle.net \
--cc=agraf@suse.de \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=tommusta@gmail.com \
/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 NNTP newsgroup(s).