type-punning to incomplete type might break strict-aliasing rules
type-punning to incomplete type might break strict-aliasing rules
- Subject: type-punning to incomplete type might break strict-aliasing rules
- From: Kenny Leung <email@hidden>
- Date: Tue, 22 Jul 2008 07:07:24 -0700
Hi All.
Just trying to keep up with the latest here. I heard many good things about llvm-gcc at WWDC. Since switching to llvm-gcc, I'm getting a lot of these warnings.
warning: type-punning to incomplete type might break strict-aliasing rules I must admit I have no idea what it really means, even after reading an explanation on the net about it. It pops up in my code when dereferencing typecast pointers. I've eliminated the few places in our code where it occurs, but I don't know how to eliminate this one. There's a warning for every use of CFSTR() to generate a constant CFString.
return CFSTR("com.quickceph.documentlegacy");
What should one do in this situation?
Thanks!
-Kenny
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden