xavi/libfixmath - Unnamed repository; edit this file 'description' to name the repository.

	Commit message (Collapse)	Author	Age	Files	Lines
*	added cmake project file	maruncz	2021-04-19	2	-88/+105
\|
*	Updated sin lut to use ~200KiB for it's table with the same accuracy, the ↵	flatmush	2011-02-25	1	-1/+1
\| \| \| \| \| \|	lookup table implementation tends to run at about 33-36% of the speed of sinf on my machine (Intel T5500). Fixed a bug in the sin lut code so that the results are always accurate. Changed fixsingen tool to generate tables correctly for the new implementation.
*	Added option to replace sin function with ~384KiB look-up table for fastest ↵	flatmush	2011-02-25	2	-12/+17
\| \| \| \| \| \|	and most accurate results. Added tool to generate sin tables. Tests indicate that using a lut is still ~2.1% out from sinf so it's very possible that our sin function is more accurate than the libmath sinf function on the computer I'm testing with. In which case the accuracy results are offset by that amount.
*	Fixed a minor error in previous commit where the wrong function name is printed.	flatmush	2011-02-25	1	-1/+6
\|
*	Added fix16_exp currently using the Taylor Series algorithm off Wikipedia, ↵	flatmush	2011-02-25	3	-14/+58
\| \| \| \| \|	if anyone can optimize this better then go ahead. Modified fixtest to be a little more generic, can now easily change which function it tests.
*	Added multi-pass approach to fixtest, now produces more accurate results. On ↵	flatmush	2011-02-24	2	-31/+37
\| \| \| \| \|	x86 with an FPU and full optimization fixed point is about 20% slower than floating point. The multi-pass approach means that this test should run unmodified on embedded environments due to lower memory usage, this test also more realistically tests for cache behaviour.
*	Minor fix regarding printf format in fixtest.	flatmush	2011-02-24	2	-2/+2
\|
*	Fixed an obvious bug, error was reported at 65536 times the correct value, ↵	flatmush	2011-02-24	2	-3/+3
\| \| \| \| \|	real value for error is between 0.0060% and 0.0085%. Changed default values to more sensible ones, though iter will need to be lowered if run on an embedded environment.
*	Added a small program called fixtest which currently tests performance and ↵	flatmush	2011-02-24	6	-0/+217
	average error on x86 platforms, currently it produces quite wildly varying results depending on the input values. The average error seems to vary between 3-8%, it's possible that setting iter to a higher value (and pass to a lower one) could give a more stable value. Fixed point seems to be slower overall on x86 (50% of float) with good floating point hardware, however with the caching enabled depending on the program the fixed point implementation may be much faster (as float would be if cached). With caching enabled there is a massive difference between and iter size below and above 4096, this is because the caching mechanism thrashes above this threshold, it probably makes sense to disable caching for these tests by compiling libfixmath with FIXMATH_NO_CACHE.