| Home | Forums | What's new | Resources | |
| libm and the saturn |
| Amon - Oct 26, 2008 |
| antime | Oct 26, 2008 | ||
| What GCC version and compiler flags are you using? Can you post a small test program that shows the problem? | |||
| Amon | Oct 28, 2008 | ||
| Where do I find this Newlib 1.16 you speak of? | |||
| mic | Oct 28, 2008 | ||
| I haven't checked which newlib version it uses, but KPIT's GNUSH is up to version 803 now iirc, so you could try updating. | |||
| Amon | Oct 28, 2008 | ||
| Currently I am waiting for approval in order to download the kpit stuff. I think I shall throw together a patch of some sort for other users of saturn orbit to use the newer stuff. | |||
| Amon | Nov 20, 2008 | |||
From KPIT support
So all i had to do was reorder the included libraries and it worked. Oh well everything is upgraded anyways | ||||
| ExCyber | Nov 20, 2008 | |||
The traditional workaround for that is to generate a look-up table of the appropriate precision/scale/type at startup/transition/whatever and use that instead of calling the function and munging its result every time you want a value. | ||||
| Amon | Nov 21, 2008 | ||
| i just reverted my code back to use the tables I created. Though I could gererate the lookup tables at startup as you suggested. Shouldnt be much difference other than precision. My table includes values for sin between 0 and 360 degrees 16bit numbers. That beats nothing. | |||