Re: Reason for -fno-strict-aliasing?

[cblake]

@Tiberium, in the `csources/build.sh` context you should only need to remove 
the `-w` and change the `-fno-strict-aliasing` in `COMP_FLAGS` since it's just 
a shell script with a zillion gcc invocations. Compiling other nim code, I only 
had to change my nim.cfg's `gcc.options.always = "-Wall 2>>/tmp/gcc.log"` or 
something similar to catch the warning outputs. Still yet to see any warnings 
related to aliasing.