public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug math/15563] sincos() is incorrect for long double and large inputs on x86_64 Date: Mon, 03 Jun 2013 17:01:00 -0000 [thread overview] Message-ID: <bug-15563-131-Z7b75mNCSZ@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-15563-131@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=15563 --- Comment #1 from joseph at codesourcery dot com <joseph at codesourcery dot com> --- I can't tell what you think the bug is here. You give a testcase for double but talk about long double, and with the obvious substitutions #define _GNU_SOURCE #include <stdio.h> #include <math.h> int main (void) { volatile long double x = 1.0e22; long double s1, s2, c1; sincosl (x, &s1, &c1); s2 = sinl (x); printf ("s1 = %.17Lg\n", s1); printf ("s2 = %.17Lg\n", s2); return 0; } I get on x86_64 (with current glibc) s1 = -0.8522008497671888 s2 = -0.8522008497671888 which appears to be what you'd expect. So what program are you building, with what options, and running with current glibc, and getting what results, and what would you like instead? -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2013-06-03 17:01 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-06-03 16:05 [Bug math/15563] New: " carlos at redhat dot com 2013-06-03 16:06 ` [Bug math/15563] " carlos at redhat dot com 2013-06-03 17:01 ` joseph at codesourcery dot com [this message] 2013-06-03 17:47 ` carlos at redhat dot com 2013-06-03 19:01 ` joseph at codesourcery dot com 2014-06-13 17:32 ` fweimer at redhat dot com
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-15563-131-Z7b75mNCSZ@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.org \ /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: linkBe 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).