public inbox for ecos-bugs@sourceware.org help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org To: unassigned@bugs.ecos.sourceware.org Subject: [Bug 1001539] Single precision floating point math library Date: Wed, 21 Mar 2012 18:36:00 -0000 [thread overview] Message-ID: <20120321183605.A88462F7800A@mail.ecoscentric.com> (raw) In-Reply-To: <bug-1001539-777@http.bugs.ecos.sourceware.org/> Please do not reply to this email. Use the web interface provided at: http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001539 --- Comment #11 from Sergei Gavrikov <sergei.gavrikov@gmail.com> 2012-03-21 18:36:01 GMT --- (In reply to comment #10) > (In reply to comment #9) > Library is not tied to any architecture, we took it from Newlib and > merely adapted to eCos by studying the differences between "double" > libs.. My standard testing is with Cortex-M3 settings -mcpu=cortex-m3 > -mthumb -O2 which is default even for Kinetis (until we switch to > gcc-4.6). > >Thus, I thought that I missed something in eCos configuration. Could > >you provide your ecm-file? > > There isn't much for ecm file, only startup type. > > It would be good if you could try with some ARM target. FYI, example > tests that fail on my platform are: asinf(x) |x| > 1, acosf(x) |x| > > 1, logf(x) x < 0. Pass: tanf(), expf(), cosf(), etc... Iljia, thanks for guidance. So, I got the same results for ARM7TDMI (LE) target (default template, RAM startup, run in GDB, build with GCC 4.6.3) ECOS_GLOBAL_CFLAGS = -Wall -Wpointer-arith -Wstrict-prototypes -Wundef -Woverloaded-virtual -Wno-write-strings -mno-thumb-interwork -mcpu=arm7tdmi -g -O2 -ffunction-sections -fdata-sections -fno-rtti -fno-exceptions ECOS_GLOBAL_LDFLAGS = -mno-thumb-interwork -mcpu=arm7tdmi -Wl,--gc-sections -Wl,-static -g -nostdlib ECOS_COMMAND_PREFIX = arm-eabi- f-tests passed: PASS:<atan2f() is stable> PASS:<atanf() is stable> PASS:<ceilf() is stable> PASS:<cosf() is stable> PASS:<coshf() is stable> PASS:<expf() is stable> PASS:<fabsf() is stable> PASS:<floorf() is stable> PASS:<fmodf() is stable> PASS:<ldexpf() is stable> PASS:<powf() is stable> PASS:<sinf() is stable> PASS:<sinhf() is stable> PASS:<sqrtf() is stable> PASS:<tanf() is stable> PASS:<tanhf() is stable> f-tests failed: FAIL:<acosf() failed tests> Line: 92, File: ... vectors/acosf.c FAIL:<asinf() failed tests> Line: 92, File: ... vectors/asinf.c FAIL:<frexpf() failed tests> Line: 92, File: ... vectors/frexpf.c FAIL:<log10f() failed tests> Line: 92, File: ... vectors/log10f.c FAIL:<logf() failed tests> Line: 92, File: ... vectors/logf.c There were 42 warnings [-Wunused-function] in the build (otherwise, all is clean). One fix would be to add a prototyping for doTestVec() and doTestVecFloat() in tests/vector_support.h with GCC attribute unused static cyg_bool doTestVec(CYG_ADDRESS func_ptr, Cyg_libm_test_arg_type arg1_type, Cyg_libm_test_arg_type arg2_type, Cyg_libm_test_arg_type result_type, const Cyg_libm_test_double_vec_t * vectors, cyg_ucount32 num_vectors) CYGBLD_ATTRIB_UNUSED; and the same for doTestVecFloat(), then build is silent. Thanks. Be continue. Sergei -- Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
next prev parent reply other threads:[~2012-03-21 18:36 UTC|newest] Thread overview: 47+ 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:40 ` 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 15:56 ` bugzilla-daemon 2012-03-21 18:36 ` bugzilla-daemon [this message] 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:06 ` 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:58 ` bugzilla-daemon 2013-06-07 9:17 ` bugzilla-daemon 2013-06-07 12:47 ` bugzilla-daemon 2013-06-07 20:20 ` bugzilla-daemon 2013-06-08 12:24 ` bugzilla-daemon 2013-06-08 15:37 ` bugzilla-daemon 2013-06-08 19:04 ` 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:59 ` 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=20120321183605.A88462F7800A@mail.ecoscentric.com \ --to=bugzilla-daemon@bugs.ecos.sourceware.org \ --cc=unassigned@bugs.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: 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).