public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bruno at clisp dot org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug math/13304] fma, fmaf, fmal produce wrong results Date: Mon, 17 Oct 2011 09:50:00 -0000 [thread overview] Message-ID: <bug-13304-131-FfUw3jGYqz@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-13304-131@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=13304 --- Comment #23 from Bruno Haible <bruno at clisp dot org> 2011-10-17 09:49:41 UTC --- (In reply to comment #22) > I've done quite a lot of testing on it back when it was added to glibc, see > e.g. the > http://sources.redhat.com/ml/libc-alpha/2010-10/txt00000.txt > testcase Good. It would be even better - for the quality of future modifications - if a good unit test was in the glibc source tree. My proposed one runs in less than a second and was able to catch 16 different bugs (and does not need to link against mpfr or gmp). > Yes, math/s_fma*.c won't DTRT, they are just fallback implementations for > architectures without sufficient exception support Find attached a code that produces the correct result also regardless of exception support. Will soon be contributed to GNU gnulib. Should we replace math/s_fma{,f,l}.c with this code (after some polishing for glibc coding style)? Bruno -- 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:[~2011-10-17 9:50 UTC|newest] Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-10-17 2:02 [Bug math/13304] New: " bruno at clisp dot org 2011-10-17 2:03 ` [Bug math/13304] " bruno at clisp dot org 2011-10-17 2:05 ` bruno at clisp dot org 2011-10-17 2:05 ` bruno at clisp dot org 2011-10-17 2:05 ` bruno at clisp dot org 2011-10-17 2:06 ` bruno at clisp dot org 2011-10-17 2:06 ` bruno at clisp dot org 2011-10-17 2:07 ` bruno at clisp dot org 2011-10-17 2:08 ` bruno at clisp dot org 2011-10-17 2:08 ` bruno at clisp dot org 2011-10-17 2:08 ` bruno at clisp dot org 2011-10-17 2:09 ` bruno at clisp dot org 2011-10-17 2:10 ` bruno at clisp dot org 2011-10-17 2:10 ` bruno at clisp dot org 2011-10-17 2:11 ` bruno at clisp dot org 2011-10-17 2:11 ` bruno at clisp dot org 2011-10-17 2:11 ` bruno at clisp dot org 2011-10-17 2:11 ` bruno at clisp dot org 2011-10-17 5:54 ` jakub at redhat dot com 2011-10-17 7:19 ` aj at suse dot de 2011-10-17 7:32 ` jakub at redhat dot com 2011-10-17 8:24 ` aj at suse dot de 2011-10-17 9:14 ` bruno at clisp dot org 2011-10-17 9:28 ` jakub at redhat dot com 2011-10-17 9:50 ` bruno at clisp dot org [this message] 2011-10-17 9:51 ` bruno at clisp dot org 2011-10-17 12:20 ` jakub at redhat dot com 2011-10-17 14:07 ` joseph at codesourcery dot com 2011-10-17 20:10 ` bruno at clisp dot org 2011-10-17 20:23 ` zimmerma+gcc at loria dot fr 2011-10-17 22:36 ` vincent-srcware at vinc17 dot net 2011-10-17 22:40 ` bruno at clisp dot org 2011-10-17 22:42 ` bruno at clisp dot org 2011-10-17 22:47 ` bruno at clisp dot org 2011-10-17 23:34 ` bruno at clisp dot org 2011-10-18 7:24 ` aj at suse dot de 2011-10-18 16:40 ` bruno at clisp dot org 2012-02-26 17:46 ` jsm28 at gcc dot gnu.org 2012-02-26 17:49 ` jsm28 at gcc dot gnu.org 2012-09-27 20:08 ` law at redhat dot com 2012-09-27 20:26 ` joseph at codesourcery dot com 2012-11-22 17:39 ` jsm28 at gcc dot gnu.org 2013-12-17 14:23 ` jsm28 at gcc dot gnu.org 2014-06-27 11:51 ` fweimer at redhat dot com 2015-09-25 17:30 ` cvs-commit at gcc dot gnu.org 2015-09-25 17:32 ` cvs-commit at gcc dot gnu.org 2015-09-25 17:35 ` jsm28 at gcc dot gnu.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-13304-131-FfUw3jGYqz@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).