This is an unofficial snapshot of the ISO/IEC JTC1 SC22 WG21 Core Issues List revision 116a. See http://www.open-std.org/jtc1/sc22/wg21/ for the official list.

2024-12-19

2964. Reading "invalid pointer values"

(From submission #645.)

Issue 2822 clarified that pointer values are not replaced by invalid pointer values when the duration of the storage of their pointee ends, but merely become invalid in the context of evaluations outside of the duration of the storage. However, 7.3.2 [conv.lval] bullet 3.3 still reads:

The result of the conversion is determined according to the following rules:

• ...
• Otherwise, if the object to which the glvalue refers contains an invalid pointer value (6.7.6.5.3 [basic.stc.dynamic.deallocation]), the behavior is implementation-defined.
• ...

Possible resolution:

Change in 7.3.2 [conv.lval] bullet 3.3 as follows:

The result of the conversion is determined according to the following rules:

• ...
• Otherwise, if the object to which the glvalue refers contains an invalid pointer value (6.7.6.5.3 [basic.stc.dynamic.deallocation]) a pointer value that is not valid in the context of the conversion (6.8.4 [basic.compound]), the behavior is implementation-defined.
• ...