public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vincent-srcware at vinc17 dot net" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug math/3976] libm rounding modes do not work correctly for many archs
Date: Wed, 29 Feb 2012 02:35:00 -0000	[thread overview]
Message-ID: <bug-3976-131-gl4TWugrpD@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-3976-131@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=3976

--- Comment #9 from Vincent Lefèvre <vincent-srcware at vinc17 dot net> 2012-02-29 02:35:24 UTC ---
Created attachment 6256
  --> http://sourceware.org/bugzilla/attachment.cgi?id=6256
Test a math function in the 4 rounding modes.

(In reply to comment #8)
> * I cannot confirm the problem with sin or cos on x86_64 (though tests should
> be added to the testsuite).

I still get the bug on the argument 100 under Debian (glibc 2.13).

> * pow (1.6, 1.6) does not segfault, but the result in round-upward mode is
> substantially inaccurate;

I confirm, but pow(1.01,1.1) crashes:

N: pow(1.01,1.1000000000000001) = 1.0110054835779234
Z: pow(1.01,1.1000000000000001) = 1.0110054835779232
D: pow(1.01,1.1000000000000001) = 1.0110054835779232
zsh: segmentation fault (core dumped)  ./tfct-4rm 1.01 1.1

> pow will need a similar fix (and test in the testsuite).

Yes, like the other functions.

> If other functions have problems in current sources, [...]

I would say that each function probably has the same problem.

I did the tests with

gcc -std=c99 tfct-4rm.c -o tfct-4rm -lm -DFCT=exp
gcc -std=c99 tfct-4rm.c -o tfct-4rm -lm -DFCT=sin
gcc -std=c99 tfct-4rm.c -o tfct-4rm -lm -DFCT=cos
gcc -std=c99 tfct-4rm.c -o tfct-4rm -lm -DFCT=pow -DTWOARGS

using the attached code.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


  parent reply	other threads:[~2012-02-29  2:35 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-3976-131@http.sourceware.org/bugzilla/>
2012-02-29  1:16 ` jsm28 at gcc dot gnu.org
2012-02-29  2:35 ` vincent-srcware at vinc17 dot net [this message]
2012-02-29  2:54 ` vincent-srcware at vinc17 dot net
2012-03-02 15:17 ` jsm28 at gcc dot gnu.org
2012-03-02 16:05 ` jsm28 at gcc dot gnu.org
2012-03-02 16:09 ` jsm28 at gcc dot gnu.org
2012-03-02 20:56 ` jsm28 at gcc dot gnu.org
2012-03-05 12:27 ` jsm28 at gcc dot gnu.org
2012-03-05 13:34 ` vincent-srcware at vinc17 dot net
2013-01-10 19:23 ` aj at suse dot de
2014-02-16 19:37 ` jackie.rosen at hushmail dot com
2014-05-28 19:40 ` schwab at sourceware dot org
2007-02-06 13:14 [Bug math/3976] New: " madcoder at debian dot org
2007-02-06 22:13 ` [Bug math/3976] " madcoder at debian dot org
2007-05-18 14:46 ` debian-glibc at lists dot debian dot org
2007-09-19 12:55 ` vincent+libc at vinc17 dot org
2008-02-25 13:12 ` vincent+libc at vinc17 dot org
2008-10-27  8:18 ` c_keil at yahoo dot de
2008-10-27  8:26 ` jakub at redhat dot com
2008-10-27  9:34 ` vincent+libc at vinc17 dot org
2008-10-27 12:43 ` joseph at codesourcery dot com
2010-03-21 22:24 ` vincent+libc at vinc17 dot org

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=bug-3976-131-gl4TWugrpD@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@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).