On Friday 30 October 2009, Debian Bug Tracking System wrote: > Steven G. Johnson wrote: > >> Whether or not such aliasing is safe is entirely dependent on > >> implementation-defined behavior, the standard leaves it undefined. > > > > This is not true. Matteo already quoted the portion of the C standard > > that specifically requires double complex and double[2] to have > > exactly the same binary representation.
Not that I still have any hope of convincing you people, but as I already demonstrated with my example code (all pointers have the same binary representation and my example aliases pointers-to-pointers), and as stated in the standard's strict aliasing rules, two types having the same binary representation does not exempt them from the strict aliasing rules.
signature.asc
Description: This is a digitally signed message part.
