public inbox for libc-hacker@sourceware.org
 help / color / mirror / Atom feed
From: Andreas Jaeger <aj@suse.de>
To: Ulrich Drepper <drepper@redhat.com>
Cc: Glibc hackers <libc-hacker@sources.redhat.com>
Subject: Re: BZ#2153: cacosh bug
Date: Sun, 15 Jan 2006 17:40:00 -0000	[thread overview]
Message-ID: <m3u0c5mluf.fsf@gromit.moeb> (raw)
In-Reply-To: <43CA85D3.9050903@redhat.com> (Ulrich Drepper's message of "Sun, 15 Jan 2006 09:26:43 -0800")

[-- Attachment #1: Type: text/plain, Size: 896 bytes --]

Ulrich Drepper <drepper@redhat.com> writes:

> 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.

So, the change to just make the sign fix in cacosh and libm-test is ok
to commit?


I'll then commit those changes and add the new tests to a new
bugreport,

Andreas
-- 
 Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj/
  SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
   GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126

[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]

  reply	other threads:[~2006-01-15 17:40 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
2006-01-15 17:40   ` Andreas Jaeger [this message]
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=m3u0c5mluf.fsf@gromit.moeb \
    --to=aj@suse.de \
    --cc=drepper@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).