From: Michael Meissner <meissner@linux.ibm.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: Michael Meissner <meissner@linux.ibm.com>,
gcc-patches@gcc.gnu.org, David Edelsohn <dje.gcc@gmail.com>,
Bill Schmidt <wschmidt@linux.ibm.com>,
Peter Bergner <bergner@linux.ibm.com>
Subject: Re: [PATCH] PowerPC: Add float128/Decimal conversions.
Date: Tue, 19 Jan 2021 12:30:31 -0500 [thread overview]
Message-ID: <20210119173031.GB1116@ibm-toto.the-meissners.org> (raw)
In-Reply-To: <20210115215244.GC30983@gate.crashing.org>
On Fri, Jan 15, 2021 at 03:52:44PM -0600, Segher Boessenkool wrote:
> On Thu, Jan 14, 2021 at 12:09:36PM -0500, Michael Meissner wrote:
> > [PATCH] PowerPC: Add float128/Decimal conversions.
>
> Same question here.
In your last message, you said that it was unacceptable that the conversion
fails if the user uses an old GLIBC. So I rewrote the code using weak
references. If the user has at least GLIBC 2.32, it will use the IEEE 128-bit
string support in the library.
If an older GLIBC is used, I then use the IBM 128-bit format as an intermediate
value. Obviously there are cases where IEEE 128-bit can hold values that IBM
128-bit can't (mostly due to the increased exponent range in IEEE 128-bit), but
it at least does the conversion for the numbers in the common range.
In doing this transformation, I needed to do minor edits to the main decimal
to/from binary conversion functions to allow the KF functions to be declared.
Previously, I used preprocessor magic to rename the functions.
--
Michael Meissner, IBM
IBM, M/S 2506R, 550 King Street, Littleton, MA 01460-6245, USA
email: meissner@linux.ibm.com, phone: +1 (978) 899-4797
next prev parent reply other threads:[~2021-01-19 17:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-14 17:09 Michael Meissner
2021-01-15 21:52 ` Segher Boessenkool
2021-01-19 17:30 ` Michael Meissner [this message]
2021-01-26 23:43 ` [Ping] " Michael Meissner
2021-01-28 3:11 ` Segher Boessenkool
2021-01-28 18:10 ` Michael Meissner
2021-01-28 18:59 ` Segher Boessenkool
2021-01-28 19:30 ` Michael Meissner
2021-01-28 19:47 ` Segher Boessenkool
2021-01-28 19:58 ` Peter Bergner
2021-01-28 21:26 ` Segher Boessenkool
2021-01-29 2:45 ` Michael Meissner
2021-01-27 21:05 ` [PATCH, revised] " Michael Meissner
2021-01-27 21:19 ` [PATCH, revised, #2] " Michael Meissner
-- strict thread matches above, loose matches on Subject: below --
2020-11-20 0:05 [PATCH] " Michael Meissner
2020-12-11 19:51 ` Segher Boessenkool
2020-12-17 18:09 ` Michael Meissner
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=20210119173031.GB1116@ibm-toto.the-meissners.org \
--to=meissner@linux.ibm.com \
--cc=bergner@linux.ibm.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=segher@kernel.crashing.org \
--cc=wschmidt@linux.ibm.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 read-only IMAP folder(s) and NNTP newsgroup(s).