Andrew Pinski wrote: > > Wrong, try again. Violating aliasing rules cause undefined behavior > so seg faulting is an okay thing to do.
But producing a warning message and bad code is not OK. Either using a "type-punned pointer" should be treated as a fatal error, because gcc would create bad code, or gcc should create working code. If gcc knows that the code is bad, why does it continue? Regards Harri
signature.asc
Description: OpenPGP digital signature
