From: Steven Munroe <munroesj@us.ibm.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Ulrich Drepper <drepper@redhat.com>,
Glibc hackers <libc-hacker@sources.redhat.com>
Subject: Re: [PATCH] Fix ppc{,64} nextafterl and fpclassifyl
Date: Thu, 07 Jun 2007 15:50:00 -0000 [thread overview]
Message-ID: <46682D96.4040904@us.ibm.com> (raw)
In-Reply-To: <20070605155638.GO3081@sunsite.mff.cuni.cz>
Jakub Jelinek wrote:
> Hi!
>
> Attached is a fixed version of nextafterl and fpclassifyl fixes Steven
> sent privately a few days ago, together with a couple of fixes on top
> of that from me.
>
This looks good, tested on powerpc32-nofpu, powerpc32, and powerpc64.
Thanks again!
> I have used attached tester to test whether nextafterl works correctly,
> not sure if we want that in glibc testsuite (only tested on ppc/ppc64
> as it is ldbl-128ibm specific) or not, perhaps with smaller number of
> tests. The 10 million iterations take ~ 70 seconds on my G5.
>
>
Additional testing is clearly needed, but where would this fit into the
tree. It is only ppc? I though other platforms where at least looking at
ldbl-128ibm?
prev parent reply other threads:[~2007-06-07 15:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-05 15:54 Jakub Jelinek
2007-06-07 15:50 ` Steven Munroe [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=46682D96.4040904@us.ibm.com \
--to=munroesj@us.ibm.com \
--cc=drepper@redhat.com \
--cc=jakub@redhat.com \
--cc=libc-hacker@sources.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).