public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jsm28 at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug math/13851] sincosl(), sinl() and cosl(), tanl() are incorrect for large inputs on x86_64 and x86 Date: Fri, 16 Mar 2012 12:38:00 -0000 [thread overview] Message-ID: <bug-13851-131-mFNLiWmyXP@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-13851-131@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=13851 --- Comment #2 from Joseph Myers <jsm28 at gcc dot gnu.org> 2012-03-16 12:37:15 UTC --- sinl, cosl, sincosl fixed by: commit 8848d99dce1e57168a492d146f5e72195c7665a5 Author: Joseph Myers <joseph@codesourcery.com> Date: Fri Mar 16 12:28:25 2012 +0000 Implement ldbl-96 sinl / cosl / sincosl (bug 13851). tanl will need a separate fix. -- 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.
next prev parent reply other threads:[~2012-03-16 12:38 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-03-15 13:41 [Bug math/13851] New: sincosl(), sinl() and cosl() " aj at suse dot de 2012-03-15 13:48 ` [Bug math/13851] " aj at suse dot de 2012-03-15 14:58 ` [Bug math/13851] sincosl(), sinl() and cosl(), tanl() " aj at suse dot de 2012-03-15 15:01 ` aj at suse dot de 2012-03-15 15:11 ` aj at suse dot de 2012-03-15 15:33 ` aj at suse dot de 2012-03-15 15:34 ` aj at suse dot de 2012-03-16 12:38 ` jsm28 at gcc dot gnu.org [this message] 2012-03-16 20:11 ` jsm28 at gcc dot gnu.org 2013-06-03 16:05 ` carlos at redhat dot com 2013-06-03 17:47 ` carlos at redhat dot com 2014-06-26 13:58 ` 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-13851-131-mFNLiWmyXP@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: 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).