From: Jakub Jelinek <jakub@redhat.com>
To: Steve Munroe <sjmunroe@us.ibm.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:32:00 -0000 [thread overview]
Message-ID: <20040407152142.GS514@sunsite.ms.mff.cuni.cz> (raw)
In-Reply-To: <OF4B674C7A.8B99751C-ON86256E6F.005B9D83-86256E6F.005DFC7C@us.ibm.com>
On Wed, Apr 07, 2004 at 12:06:32PM -0500, Steve Munroe wrote:
> Have you made any more progress on this? We are all waiting for this to be
> resolved.
Not yet, will do after Easter.
> You mention ldbl-128ibm/ and ldbl-64-128ibm/ what do you see as the
> difference?
Similarly to ldbl-128 and ldbl-64-128. The former is a directory with
support for IEEE quad long double (ldbl-128ibm would be for IBM 2xdouble
long double format), the latter contains wrappers around dbl-64 and
ldbl-128* functions so that both sizeof (double) == sizeof (long double)
and sizeof (double) < sizeof (long double) is supported.
> 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.
That should be dbl-64/wordsize-64 subdir instead IMHO.
Jakub
prev parent reply other threads:[~2004-04-07 17:32 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
2004-04-07 17:32 ` Jakub Jelinek [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=20040407152142.GS514@sunsite.ms.mff.cuni.cz \
--to=jakub@redhat.com \
--cc=drepper@redhat.com \
--cc=libc-hacker-owner@sources.redhat.com \
--cc=libc-hacker@sources.redhat.com \
--cc=rth@redhat.com \
--cc=sjmunroe@us.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).