Is a^a or a-a undefined behaviour if a is not initialized?

by

In C11:

  • It’s explicitly undefined according to 6.3.2.1/2 if a never has its address taken (quoted below)
  • It could be a trap representation (which causes UB when accessed). 6.2.6.1/5:

Certain object representations need not represent a value of the object type.

Unsigned ints can have trap representations (e.g. if it has 15 precision bits and 1 parity bit, accessing a could cause a parity fault).

6.2.4/6 says that the initial value is indeterminate and the definition of that under 3.19.2 is either an unspecified value or a trap representation.

Further: in C11 6.3.2.1/2, as pointed out by Pascal Cuoq:

If the lvalue designates an object of automatic storage duration that could have been
declared with the register storage class (never had its address taken), and that object
is uninitialized (not declared with an initializer and no assignment to it has been
performed prior to use), the behavior is undefined.

This doesn’t have the exception for character types, so this clause appears to supersede the preceding discussion; accessing x is immediately undefined even if no trap representations exist. This clause was added to C11 to support Itanium CPUs which do actually have a trap state for registers.

Systems without trap representations: But what if we throw in &x; so that that 6.3.2.1/2’s objection no longer applies, and we are on a system that is known to have no trap representations? Then the value is an unspecified value.
The definition of unspecified value in 3.19.3 is a bit vague, however it is clarified by DR 451, which concludes:

  • An uninitialized value under the conditions described can appear to change its value.
  • Any operation performed on indeterminate values will have an indeterminate value as a result.
  • Library functions will exhibit undefined behavior when used on indeterminate values.
  • These answers are appropriate for all types that do not have trap representations.

Under this resolution, int a; &a; int b = a - a; results in b having indeterminate value still.

Note that if the indeterminate value is not passed to a library function, we are still in the realm of unspecified behaviour (not undefined behaviour). The results may be weird, e.g. if ( j != j ) foo(); could call foo, but the demons must remain ensconced in the nasal cavity.

More Related Contents:

  1. Given the state of the stack and registers, can we predict the outcome of printf’s undefined behavior
  2. Why are these constructs using pre and post-increment undefined behavior?
  3. (Why) is using an uninitialized variable undefined behavior?
  4. Can we change the value of an object defined with const through pointers?
  5. Is the “struct hack” technically undefined behavior?
  6. Is accessing a global array outside its bound undefined behavior?
  7. How undefined is undefined behavior?
  8. A question about union in C – store as one type and read as another – is it implementation defined?
  9. When is casting between pointer types not undefined behavior in C?
  10. Is the output of printf (“%d %d”, c++, c); also undefined?
  11. What is Undefined Behaviour in C? [duplicate]
  12. 32 bit unsigned multiply on 64 bit causing undefined behavior?
  13. In C99, is f()+g() undefined or merely unspecified?
  14. Unspecified, undefined and implementation defined behavior WIKI for C
  15. How to implement memmove in standard C without an intermediate copy?
  16. Is this undefined C behaviour?
  17. Why does a program accessing illegal pointer to pointer not crash?
  18. Is while(1); undefined behavior in C?
  19. Does C have an equivalent of std::less from C++?
  20. Order of evaluation of arguments in function calling?
  21. C code with undefined results, compiler generates invalid code (with -O3)
  22. printf() with no arguments in C compiles fine. how?
  23. When is it valid to access a pointer to a “dead” object?
  24. Is it Undefined Behaviour to cast away the constness of a function parameter?
  25. C – is an indeterminate value indeterminable?
  26. Does ctype.h still require unsigned char?
  27. Why is undefined behaviour allowed in C
  28. Cast T[][] to T*
  29. 2D Array indexing – undefined behavior?
  30. Uninitialized variable in C [duplicate]

Leave a Comment