Question

In ISO/IEC 9899:TC2, the standard says following

6.3.2.3 Pointers

1. A pointer to an object or incomplete type may be converted to a pointer to a different
   object or incomplete type. If the resulting pointer is not correctly aligned for the pointed-to type, the behavior is undefined. Otherwise, when converted back again, the result shall compare equal to the original pointer. When a pointer to an object is converted to a pointer to a character type, the result points to the lowest addressed byte of
   the object. Successive increments of the result, up to the size of the object, yield pointers to the remaining bytes of the object.

So, it is not clear from the standard that a pointer of one type can be casted to pointer of another type.

Answer 1

Strict aliasing rule is defined somewhere else. This is the wording:

C (ISO/IEC 9899:1999 6.5/7):

An object shall have its stored value accessed only by an lvalue
expression that has one of the following types:

• a type compatible with the effective type of the object,
• a qualified version of a type compatible with the effective type of
  the object,
• a type that is the signed or unsigned type corresponding to the
  effective type of the object,
• a type that is the signed or unsigned type corresponding to a
  qualified version of the effective type of the object,
• an aggregate or union type that includes one of the aforementioned
  types among its members (including, recursively, a member of a
  subaggregate or contained union), or
• a character type.

C++ (ISO/IEC 14882:2011 3.10 [basicl.lval] / 15):

If a program attempts to access the stored value of an object through
an lvalue of other than one of the following types the behavior is
undefined:

• the dynamic type of the object,
• a cv-qualified version of the dynamic type of the object,
• a type similar (as defined in 4.4) to the dynamic type of the object,
• a type that is the signed or unsigned type corresponding to the
  dynamic type of the object,
• a type that is the signed or unsigned type corresponding to a
  cv-qualified version of the dynamic type of the object,
• an aggregate or union type that includes one of the aforementioned
  types among its elements or non-static data members (including,
  recursively, an element or non-static data member of a subaggregate
  or contained union),
• a type that is a (possibly cv-qualified) base class type of the
  dynamic type of the object,
• a char or unsigned char type.

---

The C standard doesn’t prohibit you from casting the pointer to an unrelated type, provided there are no allignment problems. However, due to the strict aliasing rule, you basically can’t dereference a pointer obtained from such a cast. So the only useful thing to do with such “invalid” pointer is to cast it back to the correct type (or a compatible type).

It’s mostly the same in C++ with reinterpret_cast (5.2.10 [expr.reinterpret.cast] / 7):

An object pointer can be explicitly converted to an object pointer of a different type. When a prvalue v of type “pointer to T1” is converted to the type “pointer to cv T2”, the result is static_cast<cv T2*>(static_cast<cv void*>(v)) if both T1 and T2 are standard-layout types (3.9) and the alignment requirements of T2 are no stricter than those of T1, or if either type is void. Converting a prvalue of type “pointer to T1” to the type “pointer to T2” (where T1 and T2 are object types and where the alignment requirements of T2 are no stricter than those of T1) and back to its original type yields the original pointer value. The result of any other such pointer conversion is unspecified.