public inbox for ecos-patches@sourceware.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org
To: ecos-patches@ecos.sourceware.org
Subject: [Bug 1001539] Single precision floating point math library
Date: Fri, 07 Jun 2013 20:20:00 -0000	[thread overview]
Message-ID: <bug-1001539-104-ho2ezz62ze@http.bugs.ecos.sourceware.org/> (raw)
In-Reply-To: <bug-1001539-104@http.bugs.ecos.sourceware.org/>

Please do not reply to this email, use the link below.

http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001539

--- Comment #27 from Ilija Kocho <ilijak@siva.com.mk> ---
(In reply to comment #25)
> Ilija, I have tested the current patches on the "psim" target (big-endian).
> 
> In the default configuration (CYGNUM_LIBM_COMPATIBILITY), I see 5 libm test
> failures (out of tolerance):  frexpf, asinf, logf, acosf, log10f
> 
> In IEEE-only configuration (CYGSEM_LIBM_COMPAT_IEEE_ONLY), I get a build
> error (EDOM undeclared). If I fix the build error by including <errno.h>
> unconditionally from vector_support_float.h then I see 1 libm test failure
> (out of tolerance):  frexpf
> 
> I hope this helps.

I reproduced your tests and it come back to me. In case of default
CYGNUM_LIBM_COMPATIBILITY configuration the real error is EDOM, but POSIX model
doesn't seem to support it. The cases that test EDOM should be excluded for
POSIX. (Please see comment 21 and patch sample below.

frexpf on the other hand seem to fail and we need to check why.



--- patch sample -----------


--- logf.h    2013-06-07 20:56:07.943683244 +0200
+++ logf_new.h    2013-06-07 20:56:16.235683588 +0200
@@ -63,12 +63,12 @@
 #include <cyg/infra/cyg_type.h>    // Common type definitions and support
 #include "vectors/vector_support_float.h"// extra support for math tests

-//#define LOG_TOLERANCE 1.0E-04
-#define LOG_TOLERANCE 1.0E-05
+#define LOG_TOLERANCE 1.0E-04

 static const Cyg_libm_test_float_vec_t logf_vec[] = {

-// AUTOMATICALLY GENERATED VECTORS START
+    // AUTOMATICALLY GENERATED VECTORS START
+#if defined CYGNUM_LIBM_COMPATIBILITY_IEEE || defined
CYGSEM_LIBM_COMPAT_IEEE_ONLY
 {0, 3214514586u, 1115684864u, 2143289344u, EDOM, LOG_TOLERANCE, 0},
 {1, 3214430700u, 1115684864u, 2143289344u, EDOM, LOG_TOLERANCE, 0},
 {2, 3214346813u, 1115684864u, 2143289344u, EDOM, LOG_TOLERANCE, 0},
@@ -189,6 +189,7 @@
 {117, 3170222735u, 1115684864u, 2143289344u, EDOM, LOG_TOLERANCE, 0},
 {118, 3164854026u, 1115684864u, 2143289344u, EDOM, LOG_TOLERANCE, 0},
 {119, 3156465418u, 1115684864u, 2143289344u, EDOM, LOG_TOLERANCE, 0},
+#endif //defined CYGNUM_LIBM_COMPATIBILITY_IEEE || defined
CYGSEM_LIBM_COMPAT_IEEE_ONLY
 {120, 646742016u, 3255452089u, 3255452089u, 0, LOG_TOLERANCE, 0},
 {121, 1008981770u, 3230883214u, 3230883214u, 0, LOG_TOLERANCE, 0},
 {122, 1017370378u, 3229245078u, 3229245078u, 0, LOG_TOLERANCE, 0},
@@ -309,6 +310,7 @@
 {237, 1066779279u, 1042335124u, 1042335124u, 0, LOG_TOLERANCE, 0},
 {238, 1066863165u, 1042906267u, 1042906267u, 0, LOG_TOLERANCE, 0},
 {239, 1066947052u, 1043472596u, 1043472596u, 0, LOG_TOLERANCE, 0},
+#if defined CYGNUM_LIBM_COMPATIBILITY_IEEE || defined
CYGSEM_LIBM_COMPAT_IEEE_ONLY
 {240, 3234402267u, 1115684864u, 2143289344u, EDOM, LOG_TOLERANCE, 0},
 {241, 3231108068u, 1115684864u, 2143289344u, EDOM, LOG_TOLERANCE, 0},
 {242, 3226013659u, 1115684864u, 2143289344u, EDOM, LOG_TOLERANCE, 0},
@@ -335,6 +337,7 @@
 {263, 3230662656u, 1115684864u, 2143289344u, EDOM, LOG_TOLERANCE, 0},
 {264, 3224580915u, 1115684864u, 2143289344u, EDOM, LOG_TOLERANCE, 0},
 {265, 3213675725u, 1115684864u, 2143289344u, EDOM, LOG_TOLERANCE, 0},
+#endif // defined CYGNUM_LIBM_COMPATIBILITY_IEEE || defined
CYGSEM_LIBM_COMPAT_IEEE_ONLY
 {266, 1058642330u, 3204629879u, 3204629879u, 0, LOG_TOLERANCE, 0},
 {267, 1075000115u, 1062549896u, 1062549896u, 0, LOG_TOLERANCE, 0},
 {268, 1082130432u, 1068593688u, 1068593688u, 0, LOG_TOLERANCE, 0},

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2013-06-07 20:20 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-20 19:23 [Bug 1001539] New: " bugzilla-daemon
2012-03-20 19:24 ` [Bug 1001539] " bugzilla-daemon
2012-03-20 19:26 ` bugzilla-daemon
2012-03-20 19:39 ` bugzilla-daemon
2012-03-20 19:39 ` bugzilla-daemon
2012-03-20 19:40 ` bugzilla-daemon
2012-03-20 19:41 ` bugzilla-daemon
2012-03-20 19:43 ` bugzilla-daemon
2012-03-20 19:47 ` bugzilla-daemon
2012-03-21 13:44 ` bugzilla-daemon
2012-03-21 15:56 ` bugzilla-daemon
2012-03-21 18:36 ` bugzilla-daemon
2012-03-21 19:52 ` bugzilla-daemon
2012-03-22 10:24 ` bugzilla-daemon
2012-03-22 10:25 ` bugzilla-daemon
2012-03-22 10:26 ` bugzilla-daemon
2012-03-22 10:27 ` bugzilla-daemon
2012-03-22 10:28 ` bugzilla-daemon
2012-03-22 11:01 ` bugzilla-daemon
2012-03-22 13:42 ` bugzilla-daemon
2012-03-22 18:05 ` bugzilla-daemon
2012-03-22 23:53 ` bugzilla-daemon
2012-08-08 11:48 ` bugzilla-daemon
2013-05-15 20:00 ` bugzilla-daemon
2013-05-16  9:59 ` bugzilla-daemon
2013-06-07  9:17 ` bugzilla-daemon
2013-06-07 12:47 ` bugzilla-daemon
2013-06-07 20:20 ` bugzilla-daemon [this message]
2013-06-08 12:24 ` bugzilla-daemon
2013-06-08 15:37 ` bugzilla-daemon
2013-06-08 19:04 ` bugzilla-daemon
2013-06-08 19:08 ` bugzilla-daemon
2013-06-08 19:39 ` bugzilla-daemon
2013-06-09  9:39 ` bugzilla-daemon
2013-06-09  9:42 ` bugzilla-daemon
2013-06-09 18:23 ` bugzilla-daemon
2013-06-28 15:42 ` bugzilla-daemon
2013-06-28 15:44 ` bugzilla-daemon
2013-06-28 15:46 ` bugzilla-daemon
2013-06-28 15:51 ` bugzilla-daemon
2013-06-28 15:52 ` bugzilla-daemon
2013-06-28 15:53 ` bugzilla-daemon
2013-06-28 15:55 ` bugzilla-daemon
2013-06-28 15:56 ` bugzilla-daemon
2013-06-28 15:57 ` bugzilla-daemon
2013-06-28 15:58 ` bugzilla-daemon
2013-06-28 17:26 ` bugzilla-daemon
2013-08-09 15:44 ` bugzilla-daemon
2013-08-25 15:41 ` bugzilla-daemon
2013-09-24 18:08 ` bugzilla-daemon

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-1001539-104-ho2ezz62ze@http.bugs.ecos.sourceware.org/ \
    --to=bugzilla-daemon@bugs.ecos.sourceware.org \
    --cc=ecos-patches@ecos.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: 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).