Disable runtime floating point exceptions

[sturnclaw]

Clang 15+ / GCC 13+ leave us no choice but to disable floating point exceptions. Their auto-vectorization optimizations load invalid values and will cause FPEs even when fp-strict is enabled.

Reference #5601.

@d3rp please confirm this PR fixes the issue on GCC 13.

[impaktor]

I guess we could also reference:
llvm/llvm-project#63708

[d3rp]

I built this PR on g++-12, g++-13 and clang++ (15.0.7) and all of them could start from Mars without crashing. Crashing was the result of the previous bug. Seems good to me!

There was an intermittent bug on the UI that shows the starting details after pressing "New Game". The starting cash and name were positioned on top of each other, but I couldn't replicate this. It is probably due to the design of drawing stuff in the upper left corner and repositioning them on their supposed positions, as that behavior shows as a quick flicker upon opening the scene (pressing "New Game")

[zonkmachine]

There was an intermittent bug on the UI that shows the starting details after pressing "New Game". The starting cash and name were positioned on top of each other, but I couldn't replicate this

This is fixed in #5612

[d3rp]

Btw, I'm not sure if it's connected or it is a previously creeped in bug, but starting the game with --start-at a.k.a. -sa will crash on my system.

On a debug build (g++-12) the culprit seems to be UpdateStarSystemCache and the assert hits a nullptr for sec.

As -sa skips all intros and jumps straight to Mars, I guess at some point the initiation routine got changed and the calls are in wrong order.

[zonkmachine]

Btw, I'm not sure if it's connected or it is a previously creeped in bug, but starting the game with --start-at a.k.a. -sa will crash on my system.

Reported here: #5285 😉

[d3rp]

Reported here: #5285 😉

Thanks - though the cause of the issue is different. I'll paste my findings there and continue on that thread.