[libvirt] [PATCH 0/3] Fix aliasing rules warnings with gcc-4.4
Mark McLoughlin
markmc at redhat.com
Fri Feb 13 11:54:08 UTC 2009
Hi,
It seems gcc's strict aliasing rules got stricter with gcc-4.4.
The basic rule is that two pointers of different types can't be
used to reference the same address in memory. One exception is
using a char* and another is when different types are members
of a union.
I've used unions to fix all the warnings I see with current
CVS HEAD. I can't say I like the solution all that much, so
if anyone has better ideas ...
Cheers,
Mark.
More information about the libvir-list
mailing list