public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Horst von Brand <vonbrand@sleipnir.valparaiso.cl>
To: Shimpei Yamashita <shimpei+usenet+.mil+.gov@BOFH.submm.caltech.edu>
Cc: mlist-egcs@nntp-server.caltech.edu
Subject: Re: asinh() gives NaN on Linux/x86/glibc with optimization on
Date: Tue, 22 Dec 1998 19:52:00 -0000	[thread overview]
Message-ID: <199812230232.XAA04922@sleipnir.valparaiso.cl> (raw)
In-Reply-To: <75pbnk$lj9@gap.cco.caltech.edu>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 742 bytes --]

Shimpei Yamashita <shimpei+usenet+.mil+.gov@BOFH.submm.caltech.edu> said:
> H.J. Lu <hjl@lucon.org> writes:
> >> On RedHat Linux 5.2 (using glibc 2.0.7) for x86, asinh() returns NaN
> >> for negative arguments if optimizations are on. The error does not
> >> occur if optimizations are turned off. I'm not sure where the problem
> >> is--egcs or glibc. Using libc5 seems to solve the problem, but so does
> >> dropping back to gcc 2.7.2.

The case given works reasonably with egcs-19981213, glibc-2.0.108 with -O2
-fomit-frame-pointer and without optimization (non-inlined asinh()).
-- 
Horst von Brand                             vonbrand@sleipnir.valparaiso.cl
Casilla 9G, Viña del Mar, Chile                               +56 32 672616

  parent reply	other threads:[~1998-12-22 19:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <egcs.m0zsbWu-00038vC@ocean.lucon.org>
1998-12-22 15:59 ` Shimpei Yamashita
1998-12-22 16:05   ` H.J. Lu
1998-12-22 19:52   ` Horst von Brand [this message]
     [not found] <egcs.m0zsbnn-00038vC@ocean.lucon.org>
1998-12-22 17:29 ` Shimpei Yamashita
1998-12-22 19:51   ` Jeffrey A Law
1998-12-22 22:34     ` H.J. Lu
1998-12-22 15:20 Shimpei Yamashita
1998-12-22 15:48 ` H.J. Lu

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=199812230232.XAA04922@sleipnir.valparaiso.cl \
    --to=vonbrand@sleipnir.valparaiso.cl \
    --cc=mlist-egcs@nntp-server.caltech.edu \
    --cc=shimpei+usenet+.mil+.gov@BOFH.submm.caltech.edu \
    /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).