[PATCH] C undefined behavior fix

[Florian Weimer]

Linus Torvalds <torvalds@transmeta.com> writes:

> To paraphrase:
>  Two implementation-defines does not make a undefine.

I don't think you can assume that an implementation-defined pointer
value can be safely dereferenced, without triggering undefined
behavior.

> Yes, gcc forgets about "what is a pointer" when it gets to the RTL layer.
> Yes, that means that alias analysis at that level simply is not valid. But
> no, that does not mean that you can avoid the standard.

Why can't we simply break the standard?  Other people do it all the
time.