------- Comment #7 from pinskia at gcc dot gnu dot org 2005-12-07 16:19 ------- (In reply to comment #6) > Can we please have the fix for PR 14024 backported into gcc 4.1? It will be > very difficult to get upstream packages like swig for c++ fixed with regards > to the > dereferencing type-punned > pointers breaking strict-aliasing if I have to force them to use an unstable > trunk version of gcc to do so.
Why? Most of the places where aliasing violations happen are very obvious (see the example in the PR). You just need to go through every source and audit it (which should happen for overflows and all other undefined behaviors). The warning is only for helping and nothing else. There are a lot of other undefined behaviors which GCC does not warn for which most people forget to look for. One is signed overflow being undefined. If we warn for that, almost every single line would warn as a = b+c; could overflow. There are many more. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14024
