Re:Null Pointer Dereferencing Causes Undefined Behavior
by notacoward on Monday April 20, 2015 @05:26PM
(#9410973)
Casting zero to a pointer yields a null pointer. That doesn't preclude other-valued null pointers, or ensure that a cast the other way will yield zero. That's where the "undefined" part comes from.
[ Parent
| on HN ]
Re:Null Pointer Dereferencing Causes Undefined Behavior
by _kst_ on Monday April 20, 2015 @06:11PM
(#9411172)
Casting a constant zero to a pointer type yields a null pointer. The conversion is done at compile time, so the compiler knows that a null pointer is the required result.
There is no requirement for an integer-to-pointer conversion to retain the bit pattern of the integer value, any more than an integer-to-floating-point conversion is required to do so.
In most modern implementations, conversions among integer and pointer types of the same size are trivial, simply reinterpreting the bits as a value of a different type.
A conforming C or C++ compiler can use, for example, the bit pattern 0xFFFFFFFF to represent a null pointer. Converting a constant 0 to a pointer type would yield a pointer with the representation 0xFFFFFFFF. Converting a non-constant 0 to a pointer type does not necessarily yield a null pointer; the result is implementation-defined, and may be indeterminate garbage.
Re:Null Pointer Dereferencing Causes Undefined Behavior
by mpyne on Monday April 20, 2015 @05:51PM
(#9411082)
The way I like to think about it is that integer zero is the name in the C/C++ language (and runtime) for the actual null pointer, nothing more or less. In particular you can't assume anything about the integer representation of the actual null pointer.