https://gcc.gnu.org/bugzilla/show_bug.cgi?id=39322
Bug 39322 depends on bug 39117, which changed state.
Bug 39117 Summary: missed strict-aliasing warning
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=39117
What|Removed |Added
-
--- Comment #5 from reichelt at gcc dot gnu dot org 2009-03-03 20:55
---
> Actually this is not a bogus aliasing warning at all. You are accessing a
> character type as an int which is an aliasing violation.
Yeah, you're right. One can only access an int array via a char pointer, but
--- Comment #4 from pinskia at gcc dot gnu dot org 2009-02-27 22:52 ---
Related a little bit to bug 39117 or at least for the PTA side of things.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39322
--- Comment #3 from rguenth at gcc dot gnu dot org 2009-02-27 22:37 ---
The FE warning code doesn't warn for *((int *) &a + 4) because it doesn't
recognize the form. This is what we get in both cases from the C frontend
and in the second case from the C++ frontend.
The PTA warning code
