This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug objc/39753] [4.3/4.4/4.5/4.6/4.7 Regression] Objective-C(++) and C90 strict-aliasing interaction bug
- From: "nicola at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Sat, 19 Mar 2011 01:25:06 +0000
- Subject: [Bug objc/39753] [4.3/4.4/4.5/4.6/4.7 Regression] Objective-C(++) and C90 strict-aliasing interaction bug
- Auto-submitted: auto-generated
- References: <bug-39753-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39753
--- Comment #11 from Nicola Pero <nicola at gcc dot gnu.org> 2011-03-19 01:24:47 UTC ---
Having looked at some of the warnings generated in GNUstep if you compile
with -fstrict-aliasing, they seem to be C warnings with little relevance
to Objective-C (they mostly seem to be due to casting to (void **)).
So on that side (the warnings) I guess I am inclined to join Mike and become
skeptical of this issue.
Unless the original report was that using -fstrict-aliasing would miscompile
Objective-C code ? We need an example though.
Thanks