Does “undefined behaviour” extend to compile-time?

by

“You’re all ignoring the actual definition and focusing on the note, The standard imposes no requirements.” – @R.MartinhoFernandes

The message above was written by the given user in Lounge<C++> and makes a very valid argument; the standard doesn’t impose any requirements when it comes to code that invokes undefined behavior.

! ! !

undefined-behavior stretches even to the far corner of parsing the input data (ie. code) by the compiler, as verified with the below quotations from both the C++11 and C99 standards.

To answer your question with one sentence;

  • undefined behavior is not limited to runtime execution, and it’s permissible to crash during compilation “in a documented manner characteristic of the environment” 1

“in a documented manner characteristic of the environment” is a kind of odd statement, you could pretty much write a compiler documenting that it might crash upon any given code (that’s invalid) to grant it the possibility to crash whenever it wants to.

1. quote from the C++11/C99 standards

###c++11

###1.3.24 [defns.undefined]

Undefined behavior; behavior for which this International Standard
imposes no requirements

[ Note:

Undefined behavior may be expected
when this International Standard omits any explicit definition of
behavior or when a program uses an erroneous construct or erroneous
data.

Permissible undefined behavior ranges from ignoring the situation completely with unpredictable results, to behaving during translation
or program execution in a documented manner characteristic of the
environment (with or without the issuance of a diagnostic message), to
terminating a translation or execution (with the issuance of a
diagnostic message).

Many erroneous program constructs do not engender undefined behavior;
they are required to be diagnosed.

— end note ]

###c99

3.4.3 – Undefined Behavior

  1. behavior, upon use of a nonportable or erroneous program construct or of erroneous data, for which this >International Standard imposes no requirements

  2. NOTE Possible undefined behavior ranges from ignoring the situation completely with unpredictable results, to behaving during translation
    or program execution     in a documented manner characteristic of the
    environment (with or without the issuance of a diagnostic message), to
    terminating a translation or execution     (with the issuance of a
    diagnostic message).

More Related Contents:

  1. When does a constexpr function get evaluated at compile time?
  2. Is sizeof in C++ evaluated at compilation time or run time?
  3. Undefined behavior and sequence points
  4. What are all the common undefined behaviours that a C++ programmer should know about? [closed]
  5. Accessing inactive union member and undefined behavior?
  6. When does invoking a member function on a null instance result in undefined behavior?
  7. Optimizing away a “while(1);” in C++0x
  8. Does initialization entail lvalue-to-rvalue conversion? Is `int x = x;` UB?
  9. Does “Undefined Behavior” really permit *anything* to happen? [duplicate]
  10. How could pairing new[] with delete possibly lead to memory leak only?
  11. Where exactly does C++ standard say dereferencing an uninitialized pointer is undefined behavior?
  12. Is right shift undefined behavior if the count is larger than the width of the type?
  13. May I take the address of the one-past-the-end element of an array? [duplicate]
  14. Are memory leaks “undefined behavior” class problem in C++?
  15. Are multiple mutations within initializer lists undefined behavior?
  16. Can I obtain C++ type names in a constexpr way?
  17. How do we explain the result of the expression (++x)+(++x)+(++x)?
  18. Virtual destructor and undefined behavior
  19. Is infinite loop still undefined behavior in C++ if it calls shared library?
  20. Why is locking a std::mutex twice ‘Undefined Behaviour’?
  21. What is a dangling reference? [duplicate]
  22. Mixing class and struct
  23. Is there a platform or situation where dereferencing (but not using) a null pointer to make a null reference will behave badly?
  24. Is it allowed to cast away const on a const-defined object as long as it is not actually modified?
  25. Can branches with undefined behavior be assumed unreachable and optimized as dead code?
  26. C++ static_cast runtime overhead
  27. How disastrous is integer overflow in C++?
  28. behavior of const_cast in C++ [duplicate]
  29. In which versions of the C++ standard does “(i+=10)+=10” have undefined behaviour?
  30. Fun with uninitialized variables and compiler (GCC)

Leave a Comment