Why is the phrase: “undefined behavior means the compiler can do anything it wants” true?

by

Nothing “causes” this to occur. Undefined behaviour cannot “occur”. There is no mystical force that descends upon your computer and suddenly makes it create black holes inside of cats.

That anything can happen when you run a program whose behaviour is undefined, is stated as fact by the C++ standard. It’s a statement of leeway, a handy excuse used by compilers to make assumptions about your code so as to provide useful optimisations.

For example, if we say that dereferencing nullptr is undefined (which it is) then no compiler needs to ever check that a pointer is not nullptr: it can just assume that a dereferenced pointer will never be nullptr, and if it’s not then any consequences are the programmer’s problem.

Due to the astounding complexity of compilers, some of those consequences can be rather unexpected.

Of course it is not actually true that “anything can happen”. Your computer has neither the necessary physical power nor the necessary legal authority to instantiate a black hole inside of a cat. But since C++ is an abstraction, it seems only fitting that we use abstractions to teach people not to write programs with undefined behaviour. If you program rigorously, assuming that “anything can happen” if your program has undefined behaviour, then you will not be surprised by said rather unexpected consequences, and you will not be tempted to try to “control” the outcome in any way.

More Related Contents:

  1. Fun with uninitialized variables and compiler (GCC)
  2. Redefinition C++ Issue, Multiple Header
  3. How does the compilation/linking process work?
  4. Has C++ standard changed with respect to the use of indeterminate values and undefined behavior in C++14?
  5. Why is unsigned integer overflow defined behavior but signed integer overflow isn’t?
  6. Do I need to cast to unsigned char before calling toupper(), tolower(), et al.?
  7. May I treat a 2D array as a contiguous 1D array?
  8. Undefined behavior and sequence points reloaded
  9. Why do constant expressions have an exclusion for undefined behavior?
  10. How is a variable at the same address producing 2 different values? [duplicate]
  11. Constants and compiler optimization in C++
  12. Why dereferencing a null pointer is undefined behaviour?
  13. Why should I not try to use “this” value after “delete this”?
  14. C++ compilation bug?
  15. How to check if C++ compiler uses IEEE 754 floating point standard
  16. Is this infinite recursion UB?
  17. what is “stack alignment”?
  18. When do compilers inline C++ code?
  19. Compiling with g++ using multiple cores
  20. How is static variable initialization implemented by the compiler?
  21. What is Linux utility to mangle a C++ symbol name?
  22. new() without delete() is Undefined Behavior or merely Memory Leak? [duplicate]
  23. Why include guards?
  24. Near constant time rotate that does not violate the standards
  25. Undefined behavior causing time travel
  26. Why doesn’t vector::clear remove elements from a vector?
  27. Setting extra bits in a bool makes it true and false at the same time
  28. Two ‘==’ equality operators in same ‘if’ condition are not working as intended
  29. Can undefined behavior erase the hard drive?
  30. Does an R compiler to C/C++ exist?

Leave a Comment