In my university times I wrote a library (to help with some homework we gave students) that calculated the CRC32 for ethernet.
Which worked well unless compiled with `strict-aliasing` gcc optimizations enabled...
Just writing UDP RFC compliant code doesn't protect you from running into annoying behavior with your programming language of choice...
> Which worked well unless compiled with `strict-aliasing` gcc optimizations enabled
I can't imagine enabling this by default instead of opting in with __restrict or equivalent. Just so many things that could go wrong if every little piece of code was not written with aliasing in mind.