Runtime does not compile when Has_FPU is set to False

[adacore]

Runtime does not compile when Has_FPU is set to False

[NicoPy]

I have understood how the FPU configuration works (for ARM architecture).
Here it is for reference.

cortexm.py is used to configure the runtime sources/configuration :

• has_fpu() property must always be set to True else the runtime does not compile.

• To use software floating point calculations, has_single_precision_fpu() and has_double_precision_fpu() properties must return False. You also have to set -msoft-float switch in compiler_switches().

• To use hardware floating point calculations, has_single_precision_fpu() or has_double_precision_fpu() or both must return True. You also have to set -mfpu=xxx switch to the correct value in compiler_switches().

In s-bbpara__xxxx.ads the constant Has_FPU is indirectly related to the runtime configuration.
When Has_FPU is True, the floating point context is saved/restored in Pend_SV_Handler() (s-bcpcst__pendsv.adb).

• To use software floating point calculations, set Has_FPU to False.
• To use hardware floating point calculations, set Has_FPU to True.

To be more complete :

has_double_precision_fpu()	has_single_precision_fpu()	-->		compiler switch	Has_FPU
False	False	-->	soft float	-msoft-float	False
False	True	-->	single precision : hard double precision : soft	-mfpu=xxx	True
True	False	-->	single precision : soft double precision : hard	-mfpu=xxx	True
True	True	-->	single precision : hard double precision : hard	-mfpu=xxx	True

[Fabien-Chouteau]

Hi @NicoPy,
I am glad you found the answer :)