fix strict aliasing violations

[rafaelvanoni]

No description provided.

[cmikk]

For the libmy changes, I've been following the convention:

1. Check if the changed function / file is actually used in the local project. If not, trim all unused files from the local project's libmy/ subdirectory.
2. Check if the change has been made at the main libmy repo. If not, and the fix is generally applicable to all users of libmy, make the fix there.
3. Update the fixed file(s) in applicable project libmy/ subdirectories in a separate commit.

The first is useful cleanup in general, as unused files in libmy/ add noise to code analysis like this.

[rafaelvanoni]

For the libmy changes, I've been following the convention:

1. Check if the changed function / file is actually used in the local project. If not, trim all unused files from the local project's libmy/ subdirectory.
2. Check if the change has been made at the main libmy repo. If not, and the fix is generally applicable to all users of libmy, make the fix there.
3. Update the fixed file(s) in applicable project libmy/ subdirectories in a separate commit.

The first is useful cleanup in general, as unused files in libmy/ add noise to code analysis like this.

Here's the libmy PR -> farsightsec/libmy#6, will follow up with the other fixes.