CWG2899 Bad value representations should cause undefined behavior

Author: burblebee

source/expressions.tex

@@ -674,11 +674,22 @@
 pointer value\iref{basic.stc.dynamic.deallocation}, the behavior is
 \impldef{lvalue-to-rvalue conversion of an invalid pointer value}.
 
+\item Otherwise, if the bits in the value representation of
+the object to which the glvalue refers
+are not valid for the object's type, the behavior is undefined.
+\begin{example}
+\begin{codeblock}
+bool f() {
+  bool b = true;
+  char c = 42;
+  memcpy(&b, &c, 1);
+  return b;         // undefined behavior if \tcode{42} is not a valid value representation for \keyword{bool}
+}
+\end{codeblock}
+\end{example}
+
 \item Otherwise, the object indicated by the glvalue is read\iref{defns.access},
 and the value contained in the object is the prvalue result.
-If the result is an erroneous value\iref{basic.indet} and
-the bits in the value representation are not valid for the object's type,
-the behavior is undefined.
 \end{itemize}
 
 \pnum