undefined | Better HN

0 pointsphkahler1y ago0 comments

>> The firmware usually runs on processors without hardware floating point units.

I'm working on control code one an ARM cortex-M4f. I wrote it all in fixed point because I don't trust an FPU to be faster, and I also like to have a 32bit accumulator instead of 24bit. I recently converted it all to floating point since we have the M4f part (f indicate FPU), and it's a little slower now. I did get to remove some limit checking since I can rely on the calculations being inside the limits but it's still a little slower than my fixed point implementation.

0 comments

sitkack1y ago

The other great thing about going fixed point is that it doesn't expose you to device specific floating point bugs, making your embedded code way more portable and easier to test.

32b float on your embedded device doesn't necessary match your 32b float running on your dev machine.

bobmcnamara1y ago

32b float can match your desktop. Really just takes a few compiler flags(like avoiding -funsafe-math), setting rounding modes, and not using the 80bit Intel mode(largely disused after 64bit transition).

sitkack1y ago

I understand what you are saying ...

You aren't guaranteed that your microcontrollers float is going to match your desktop. Microcontrollers are riddled with bugs, unless you need floats and fixedpoint is fast enough. My recommendation is still to use fixedpoint if application is high reliability.

Esp if your code needs to be portable across arm, risc-v, etc.

bobmcnamara1y ago

Many microcontrollers today, including ARM, RISC-V, and Xtensa have IEEE compliant FPUs or libms available. Same numeric format, same rounding, same result.

Fixed point isn't bad at all, just often slower when a compliant FPU is available.

1 more reply

cpeterso1y ago

Why did you decide to convert your code to floating point if your fixed point implementation was faster and already written?

gatane1y ago

Are there any good benchmarks for float vs fixed point, specially for ARM systems?

evoke49081y ago

Just look at the instruction set for your particular CPU. Every CPU is different, but in most architectures I've seen, floating point operations are 2-3 times slower for the same word size.

Single float adds are usually 2 or 3 CPU cycles while single-word integer adds are usually 1 cycle.

Again, this is extremely dependent on the particular CPU you have. Some architectures do have single-cycle FPU operations, but it's not very common in microcontrollers as far as I can tell.

EasyMark1y ago

That would vary wildly with the ARM chip you are talking about. I would say figure out which ARM you’re interested in and go down the rabbit hole from there.

j / k navigate · click thread line to collapse

0 comments

sitkack1y ago

The other great thing about going fixed point is that it doesn't expose you to device specific floating point bugs, making your embedded code way more portable and easier to test.

32b float on your embedded device doesn't necessary match your 32b float running on your dev machine.

bobmcnamara1y ago

sitkack1y ago

I understand what you are saying ...

Esp if your code needs to be portable across arm, risc-v, etc.

bobmcnamara1y ago

Many microcontrollers today, including ARM, RISC-V, and Xtensa have IEEE compliant FPUs or libms available. Same numeric format, same rounding, same result.

Fixed point isn't bad at all, just often slower when a compliant FPU is available.

1 more reply

cpeterso1y ago

Why did you decide to convert your code to floating point if your fixed point implementation was faster and already written?

gatane1y ago

Are there any good benchmarks for float vs fixed point, specially for ARM systems?

evoke49081y ago

Just look at the instruction set for your particular CPU. Every CPU is different, but in most architectures I've seen, floating point operations are 2-3 times slower for the same word size.

Single float adds are usually 2 or 3 CPU cycles while single-word integer adds are usually 1 cycle.

Again, this is extremely dependent on the particular CPU you have. Some architectures do have single-cycle FPU operations, but it's not very common in microcontrollers as far as I can tell.

EasyMark1y ago

That would vary wildly with the ARM chip you are talking about. I would say figure out which ARM you’re interested in and go down the rabbit hole from there.

j / k navigate · click thread line to collapse