[Bug c/42907] -fstrict-aliasing breaks valid code

[matz at gcc dot gnu dot org]

------- Comment #30 from matz at gcc dot gnu dot org  2010-02-01 12:24 -------
See comment #3 for how (newer) GCC does warn at line 15.  Not with the default
options, though, but this has good reasons (too many false positives).

You are right that we should be able to improve our diagnostics in this case,
as, as you say, line 15 and 22 together create a definitely fishy situation.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42907