From: Steve Munroe <sjmunroe@us.ibm.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Glibc hackers <libc-hacker@sources.redhat.com>,
Roland McGrath <roland@redhat.com>
Subject: Re: [PATCH] ppc ulps fixes
Date: Mon, 30 Jan 2006 17:16:00 -0000 [thread overview]
Message-ID: <OFB46E2CCA.5DE5C177-ON86257106.005E6BB4-86257106.005EED7C@us.ibm.com> (raw)
In-Reply-To: <20060130164109.GO4625@sunsite.mff.cuni.cz>
Jakub Jelinek <jakub@redhat.com> wrote on 01/30/2006 10:41:09 AM:
> Hi!
>
> I think it is better to merge ulps results rather than regenerate, that
way
> we don't suddenly start getting many errors when using slightly older
> compilers.
> Also, I think it is a bad idea to put
> ldouble: 17987982955981951215498976719132
> and similar into the libm-test-ulps file, only the ulps we want to
tolerate
> (< 10, < 12 or something like that).
>
I have a patch coming that fixes the underlying problems and the ppc ulps
file. I'll send it as soon we complete the internal review.
Steven J. Munroe
Linux on Power Toolchain Architect
IBM Corporation, Linux Technology Center
next prev parent reply other threads:[~2006-01-30 17:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-30 16:41 Jakub Jelinek
2006-01-30 17:16 ` Steve Munroe [this message]
2006-01-30 22:31 ` Roland McGrath
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=OFB46E2CCA.5DE5C177-ON86257106.005E6BB4-86257106.005EED7C@us.ibm.com \
--to=sjmunroe@us.ibm.com \
--cc=jakub@redhat.com \
--cc=libc-hacker@sources.redhat.com \
--cc=roland@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).