[Bug 1001539] Single precision floating point math library

[bugzilla-daemon@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 #10 from Ilija Kocho <ilijak@siva.com.mk> 2012-03-21 15:55:33 GMT ---
Hi Sergei

Thank you for testing libm.

(In reply to comment #9)
> (In reply on comment #0)
> Hi Visar,
> and Ilija
> 
> Thank you for your contribution.
> 
> Unfortunately, I have no CORTEX-M4F CPU to get all benefits the library,
> however, I guessed the library should not depend on any architecture. Is
> it correct? 

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).

>If so, should I have something special in eCos config to
> build f-tests?

Target is TWR-K60N512, Default template, just for practical reasons I'm
changing startup type from ROM to SRAM.

> Why I ask? All f-tests fail on eCos synthetic target
> (d-tests are okay). 

True some tests fail when the result is supposed to be NaN such as acosf(1.2)
The function returns 0 instad of NaN. I wander if it is a setting or the
compiler option. The same behavior with both 4.3.2 and 4.6.3.

I thought of some work-around but then decided to put it as-is - we need a
solution rather than workaround.

>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...

Thank you again
Ilija

-- 
Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.