Do you want to squash the fixup commits before merging the changes or are we fine merging it as it is?

Done. The only change I was not able to verify is whether or not 043a7b0 is the correct fix to the strict aliasing problem...

Do you want to squash the fixup commits before merging the changes or are we fine merging it as it is?

Done. The only change I was not able to verify is whether or not 043a7b0 is the correct fix to the strict aliasing problem...

I think it is correct. These are very similar changes I did in 2fa6700 when I was tackling this issue in the rest of the code. But I do not build the openpace so I probably did not hit this issue.

Did you try with -Wstrict-aliasing=2 in CFLAGS? I think this was enough to trigger the warning/error (added now into --enable-strict in configure.ac with 544dcc6.

Sorry for the late feedback. No, I wasn't able to see the warnings for the unmodified code with gcc 10.3.0 and the above flags. Could we make this strict build part of the CI process?

np. I was adding the -Wstrict-aliasing=2 in the above mentioned commit, but the linux builds do not use openpace so that parts are not executed. It should be executed on OSX though. I see the flags used there, but I am not sure what gcc/clang/compiler is used there and whether it supports this warnings correctly.

The simplest would probably be to add one more target to linux with building also openpace (It is not in the current ubuntu version in GH).