From: Steve Munroe <sjmunroe@us.ibm.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Ulrich Drepper <drepper@redhat.com>,
Glibc hackers <libc-hacker@sources.redhat.com>,
libc-hacker-owner@sources.redhat.com,
Richard Henderson <rth@redhat.com>
Subject: Re: [PATCH] long double IEEE double -> quad switch
Date: Wed, 07 Apr 2004 17:06:00 -0000 [thread overview]
Message-ID: <OF4B674C7A.8B99751C-ON86256E6F.005B9D83-86256E6F.005DFC7C@us.ibm.com> (raw)
In-Reply-To: <20040324160427.GM15946@sunsite.ms.mff.cuni.cz>
Jakub Jelinek <jakub@redhat.com> wrote on 03/24/2004 10:04:27 AM:
> Hi!
>
> The following patch allows sparc32 (and easily also alpha, s390{,x}) to
> switch from double == long double to IEEE quad long double without
> upgrading libc.so/libm.so SONAME.
> All functions which deal with long double (*printf*, *scanf*, *told*,
> q[efg]cvt*, strfmon{,_l}, *l in libm (and a few math routines in libc)
> had to be versioned and the installed headers
> allow both -mlong-double-128 (which can now be made the default
> GCC option for sparc-*-linux and other arches) and through __REDIRECTs
> (or #defines for lame compilers) -mlong-double-64.
> Tested on sparc32 (only 2x6 make check failures (6 failures in
> test-ldouble and 6 in test-ildoubl; 4 of them is a GCC bug which
optimizes
> out division by floating zero from const long double array (seems to be
> fixed in gcc 3.4), so division by zero exception is not raised,
> one is imprecise test in libm-test.inc (recently added atan2 has
> just enough digits for ldbl-96, not ldbl-128) and one is a 10 ulps
failure
> which can be probably added to ulps)) and x86-64.
Have you made any more progress on this? We are all waiting for this to be
resolved.
>
> Alpha long double support should be doable on top of this patch quite
> easily, just a few
linux/alpha/{Makefile,Implies,Versions,bits/wordsize.h}
> tweaks.
>
> PowerPC{,64} will be far more difficult if ppc is going to use
> IBM long double format as opposed to IEEE quad long double
> (basically sysdeps/ieee754/ldbl-128ibm/ and
sysdeps/ieee754/ldbl-64-128ibm/
> would need to be implemented, whereas the latter is trivial, the former
> is a lot of work).
>
I have most of this code written but we are still debugging (a number of
surprises in nextafter and fpclassify but we are making progress). So we
are ready to start submitting code but would like to see more about your
work first.
You mention ldbl-128ibm/ and ldbl-64-128ibm/ what do you see as the
difference?
I also see an opportunity to improve the double implementations for
64-bit. Should we add dbl-64-64(sp?) where the code assumes 64-bit
registers for the (long) integer bit manipulation. This should be
generally useful beyond powerpc64.
Steven J. Munroe
Linux on Power Toolchain Architect
IBM Corporation, Linux Technology Center
next prev parent reply other threads:[~2004-04-07 17:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-24 22:00 Jakub Jelinek
2004-03-27 8:18 ` Ulrich Drepper
2004-04-07 17:06 ` Steve Munroe [this message]
2004-04-07 17:32 ` Jakub Jelinek
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=OF4B674C7A.8B99751C-ON86256E6F.005B9D83-86256E6F.005DFC7C@us.ibm.com \
--to=sjmunroe@us.ibm.com \
--cc=drepper@redhat.com \
--cc=jakub@redhat.com \
--cc=libc-hacker-owner@sources.redhat.com \
--cc=libc-hacker@sources.redhat.com \
--cc=rth@redhat.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).