News for hackers. Stuff that matters.
Re:A semantic model for a substantial fragment of C by laughinghan on Sunday April 02, 2017 @04:00PM (#14018747)
I have no idea what your point is, if any.

I will note that "from [a] practical point of view ONLY", it is incredibly impractical for a compiler to gratuitously break real code that relies on behavior that deviates from spec; if that reliance is common, the practical thing to do is to support that behavior, which they do: "The optimizer does go to some effort to "do the right thing" when it is obvious what the programmer meant (such as code that does "* (int *)P" when P is a pointer to float)." --blogpost by the second most widely used C compiler, clang/llvm: http://blog.llvm.org/2011/05/what-every-c-programmer-should-...

Which is why projects like Cerberus are valuable.

Re:A semantic model for a substantial fragment of C by wruza on Monday April 03, 2017 @04:38AM (#14021387)
My point is that UB is almost never any bad, and when it is, there is a live case for that. There is no value in defining the undefined. Clang does what it does at internal levels for completely different purpose than supporting "real code that relies on behavior that deviates from spec". The article describes that in detail. That is completely disconnected from the value of Cerberus-thing you mentioned.