------- Comment #32 from emn13+gcc at nerbonne dot org 2010-02-01 13:24 ------- I realize that you *can* enable a specific warning that might solve this; but that's a pretty unsatisfactory state of affairs.
The point is that if you've old (or external) C code *anywhere* in your app which breaks due to this behavior, there's no hint of what's wrong anywhere; enabling "all" warnings doesn't actually enable the warning you need, and you're stuck. The problematic bit (to my untrained ears anyhow) isn't that the code breaks, it's that it breaks without warning and didn't previously (despite strict aliasing) and doesn't necessarily break in other compilers (just tried in msvc 10.0, for instance) - so the notion that the diagnostics could be improved should (in principle, anyhow) cover it. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42907
