Quote:
Originally Posted by JonathanWilson
I've tried to look on google but can't really find an answer.
What I'm wondering is when the different compile options are most apropriate.
My guess is that soft (full emulation) is best when there is no FPU at all.
softfp is best when there is potentially a fpu
hardfp is best when you know there is a FPU
A cpu with no FPU will be faster with soft than softfp due to the overhead of checking or capturing an error when the fpu is absent and reverting to software fpu calculations.
a cpu with a fpu will be faster with hardfp as no tests are performed/errors triggered saying no fpu available so it hits the hardware imediatly.
Would these assumptions be correct?
|
hardfp compiles inline FP instructions. If you have an FPU this will be fastest. If you don't, every FP instruction will trap to an emulation routine (assuming your runtime supports this).
softfp will compile a library call for every FP operation. Use this if you never run on a system with an FPU.
