Does not evaluating the expression to which sizeof is applied make it legal to dereference a null or invalid pointer inside sizeof in C++?

by

I believe this is currently underspecified in the standard, like many issues such as What is the value category of the operands of C++ operators when unspecified?. I don’t think it was intentional, like hvd points outs it is probably obvious to the committee.

In this specific case I think we have the evidence to show what the intention was. From GB 91 comment from the Rapperswil meeting which says:

It is mildly distasteful to dereference a null pointer as part of our specification, as we are playing on the edges of undefined behaviour. With the addition of the declval function template, already used in these same expressions, this is no longer necessary.

and suggested an alternate expression, it refers to this expression which is no longer in the standard but can be found in N3090:

noexcept(*(U*)0 = declval<U>())

The suggestion was rejected since this does not invoke undefined behavior since it is unevaluated:

There is no undefined behavior because the expression is an unevaluated operand. It’s not at all clear that the proposed change would be clearer.

This rationale applies to sizeof as well since it’s operands are unevaluated.

I say underspecified but I wonder if this is covered by section 4.1 [conv.lval] which says:

The value contained in the object indicated by the lvalue is the rvalue result. When an lvalue-to-rvalue conversion occurs
within the operand of sizeof (5.3.3) the value contained in the referenced object is not accessed, since that operator
does not evaluate its operand.

It says the value contained is not accessed, which if we follow the logic of issue 232 means there is no undefined behavior:

In other words, it is only the act of “fetching”, of lvalue-to-rvalue conversion, that triggers the ill-formed or undefined behavior

This is somewhat speculative since the issue is not settled yet.

More Related Contents:

  1. When does invoking a member function on a null instance result in undefined behavior?
  2. Accessing inactive union member and undefined behavior?
  3. Has C++ standard changed with respect to the use of indeterminate values and undefined behavior in C++14?
  4. Optimizing away a “while(1);” in C++0x
  5. Does initialization entail lvalue-to-rvalue conversion? Is `int x = x;` UB?
  6. Do I need to cast to unsigned char before calling toupper(), tolower(), et al.?
  7. Is `reinterpret_cast`ing between hardware SIMD vector pointer and the corresponding type an undefined behavior?
  8. Why does left shift operation invoke Undefined Behaviour when the left side operand has negative value?
  9. Does “Undefined Behavior” really permit *anything* to happen? [duplicate]
  10. Where exactly does C++ standard say dereferencing an uninitialized pointer is undefined behavior?
  11. What is the size of void?
  12. Difference between Undefined Behavior and Ill-formed, no diagnostic message required
  13. Is passing a C++ object into its own constructor legal?
  14. Are multiple mutations of the same variable within initializer lists undefined behavior pre C++11
  15. In C++11, does `i += ++i + 1` exhibit undefined behavior?
  16. So why is i = ++i + 1 well-defined in C++11?
  17. Why is f(i = -1, i = -1) undefined behavior?
  18. Implementing a std::vector like container without undefined behavior
  19. Are pointer variables just integers with some operators or are they “symbolic”?
  20. The behaviour of floating point division by zero
  21. Can branches with undefined behavior be assumed unreachable and optimized as dead code?
  22. Dangling references and undefined behavior
  23. In which versions of the C++ standard does “(i+=10)+=10” have undefined behaviour?
  24. Observable behavior and undefined behavior — What happens if I don’t call a destructor?
  25. Is it a conforming compiler extension to treat non-constexpr standard library functions as constexpr?
  26. When using C headers in C++, should we use functions from std:: or the global namespace?
  27. Matching alias template as template argument
  28. Do all pointers have the same size in C++?
  29. Is a constexpr array necessarily odr-used when subscripted?
  30. Does the standard mandate an lvalue-to-rvalue conversion of the pointer variable when applying indirection?

Leave a Comment