search for: know_14

...n to do >> so. > > In case you're not aware of it, here's a fairly relevant blog series on > the topic of undefined behaviour in C: > > http://blog.llvm.org/2011/05/what-every-c-programmer-should-know.html > http://blog.llvm.org/2011/05/what-every-c-programmer-should-know_14.html > http://blog.llvm.org/2011/05/what-every-c-programmer-should-know_21.html We're aware of those, thanks. >> >> At the end of the day, code is not written purely by "thinking about >> what the C language guarantees", but rather by test-and-debug cycles >&...

On 26 June 2015 at 22:53, Sean Silva <chisophugis at gmail.com> wrote: > All of these seem to fall into the pattern of "The compiler is required to > do what you expect, as long as it can't prove X about your program". That > is, the only reasonable compilation in the absence of inferring some extra > piece of information about your program, is the one you expect.