Don't use -fno-strict-aliasing for optimized build
There doesn't seem to be any need for it, the library compiles fine without it and the few warnings generated with -Wstrict-aliasing=2 are harmless (i.e. the strict aliasing rule is not really broken).
This commit is contained in: