Am Friday 28 January 2011 12:39:34 schrieb Stuart Winter:
- soft: only software emulation
- softfp + mfpu=xxx: enables the compiler to use FP
instructions/registers inside functions, but not as function
parameters. This way, code remains compatible with 'soft' libraries
- hard: it's a
Hmm, I did not really see what's the default here (soft, softfp, hard)?
Me neither - I thought that the specs there were what was used by default.
I had a further quick read about it and that isn't the case.
As soft/softfpe is some kind of porting floating point operations to integer
I've
- soft: only software emulation
- softfp + mfpu=xxx: enables the compiler to use FP
instructions/registers inside functions, but not as function
parameters. This way, code remains compatible with 'soft' libraries
- hard: it's a different ABI, where parameters can be passed in FP
registers,
Hi,
I did not really understand what's the difference between -mfloat-abi=soft
and -mfloat-abi=softfp? Does soft always use software floating point
and softfp could use hardware floating point if a correct -mfpu is given?
And why is none of them used in Armed Slack? In my understanding it
2011/1/27 Thorsten Mühlfelder thenk...@gmx.de:
Hi,
I did not really understand what's the difference between -mfloat-abi=soft
and -mfloat-abi=softfp? Does soft always use software floating point
and softfp could use hardware floating point if a correct -mfpu is given?
Exactly.
- soft: only
