Comments on: A Guide to Undefined Behavior in C and C++, Part 1

By: outerplanet

outerplanet — Sun, 23 Jan 2011 01:56:29 +0000

[...] lecture, about Undefined Behavior in c and c plus plus, at Regehr´s blog Look at the piece of code: what is going to happen [...]

By: Undefined Behavior of C and C++ | Itsy Bitsy

Undefined Behavior of C and C++ | Itsy Bitsy — Tue, 02 Nov 2010 22:27:05 +0000

[...] A Guide to Undefined Behavior in C and C++, Part 1 A Guide to Undefined Behavior in C and C++, Part 2 A Guide to Undefined Behavior in C and C++, Part 3 This entry was posted in Worth reading. Bookmark the permalink. ← Making a JUnit 4 Test Suite [...]

By: Undefined behavior in C and C++ « IPhVu::iLearn

Undefined behavior in C and C++ « IPhVu::iLearn — Wed, 27 Oct 2010 07:17:43 +0000

[...] Undefined behavior in C and C++ 19/08/2010 phvu Leave a comment Go to comments http://blog.regehr.org/archives/213 [...]

By: Steve

Steve — Wed, 25 Aug 2010 21:36:36 +0000

Cleared up my full misundertanding here…

http://stackoverflow.com/questions/3569424/how-to-do-a-double-chunk-add-with-no-undefined-behaviour

Basically, big integers without undefined behaviour have been perfectly possible for some time – the languages are (slightly, but in a very significant way) better defined than I realised, and have been for a little over ten years.

By: regehr

regehr — Mon, 23 Aug 2010 02:56:00 +0000

Hi Steve- – Yes this is exactly right: machine generated code, macros, inlining, etc. can cause bizarre source code that a human would never write. Also, most good compilers these days will perform inlining across compilation units, so it’s not really easy to predict what the code that the compiler finally sees will look like.