public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sjmunroe at us dot ibm dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug math/2466] New: Errors in long double (ldbl-128ibm) llrounding functions in glibc-2.4 Date: Thu, 16 Mar 2006 18:40:00 -0000 [thread overview] Message-ID: <20060316184051.2466.sjmunroe@us.ibm.com> (raw) The implementations of the (IBM double double format) long double (./ldbld-128ibm/) for llrintl and llroundl, round incorrectly when the integer portion is contained in th ehigh double, but the fractional postion is contained in the low double. There are also problems where the input value approaches __LONG_LONG_MAX__. Also the IEEE 1003.1 spec states "These functions shall round their argument to the nearest integer value, rounding according to the current rounding direction." So I added tests to libm-test.inc to cover llrint in four rounding modes (FE_TONEAREST, FE_TOWARDZERO, FE_UPWARD, FE_DOWNWARD) in addition to the default rounding. -- Summary: Errors in long double (ldbl-128ibm) llrounding functions in glibc-2.4 Product: glibc Version: 2.4 Status: NEW Severity: normal Priority: P2 Component: math AssignedTo: aj at suse dot de ReportedBy: sjmunroe at us dot ibm dot com CC: glibc-bugs at sources dot redhat dot com GCC build triplet: powerpc-gnu-linux GCC host triplet: powerpc-gnu-linux GCC target triplet: powerpc-gnu-linux http://sourceware.org/bugzilla/show_bug.cgi?id=2466 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next reply other threads:[~2006-03-16 18:40 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-03-16 18:40 sjmunroe at us dot ibm dot com [this message] 2006-03-16 18:47 ` [Bug math/2466] " sjmunroe at us dot ibm dot com 2006-03-16 18:52 ` sjmunroe at us dot ibm dot com 2006-03-16 18:55 ` sjmunroe at us dot ibm dot com 2006-03-16 23:17 ` cvs-commit at gcc dot gnu dot org 2006-04-23 17:47 ` drepper at redhat dot com 2006-05-11 13:56 ` sjmunroe at us dot ibm 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=20060316184051.2466.sjmunroe@us.ibm.com \ --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).