From: Ulrich Drepper <drepper@redhat.com>
To: Andreas Jaeger <aj@suse.de>
Cc: Glibc hackers <libc-hacker@sources.redhat.com>
Subject: Re: BZ#2153: cacosh bug
Date: Sun, 15 Jan 2006 17:25:00 -0000 [thread overview]
Message-ID: <43CA85D3.9050903@redhat.com> (raw)
In-Reply-To: <m3bqydpkco.fsf@gromit.moeb>
[-- Attachment #1: Type: text/plain, Size: 539 bytes --]
Andreas Jaeger wrote:
>
> +ildouble: 735
> +ldouble: 735
>
> Function: Imaginary part of "cacosh":
> double: 1
> float: 3
> idouble: 1
> ifloat: 3
> -ildouble: 1
> -ldouble: 1
> +ildouble: 119
> +ldouble: 119
If there are error ranges like this there is clearly something wrong.
This has to be fixed.
Separate out the sign fix from adding the new test cases and file a bug
for the new tests, pointing to the high ulps.
--
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 251 bytes --]
next prev parent reply other threads:[~2006-01-15 17:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-15 15:44 Andreas Jaeger
2006-01-15 17:25 ` Ulrich Drepper [this message]
2006-01-15 17:40 ` Andreas Jaeger
2006-01-15 17:47 ` Ulrich Drepper
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=43CA85D3.9050903@redhat.com \
--to=drepper@redhat.com \
--cc=aj@suse.de \
--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).