Small tweak to documentation of scalar_storage_order

gcc/
	PR c/100653
	* doc/extend.texi (scalar_storage_order): Rephrase slightly.

diff --git a/gcc/doc/extend.texi b/gcc/doc/extend.texi
index 3ddeb0dee3a631ad6f2bfb1f9b880010cfa69064..bfe9c21bddfa0c16fe96aa0c48c531f3c3609ef2 100644 (file)
--- a/gcc/doc/extend.texi
+++ b/gcc/doc/extend.texi
@@ -8586,8 +8586,9 @@ The second case is nevertheless allowed to be able to perform a block copy
 from or to the array.
 
 Moreover, the use of type punning or aliasing to toggle the storage order
-is not supported; that is to say, a given scalar object cannot be accessed
-through distinct types that assign a different storage order to it.
+is not supported; that is to say, if a given scalar object can be accessed
+through distinct types that assign a different storage order to it, then the
+behavior is undefined.
 
 @item transparent_union
 @cindex @code{transparent_union} type attribute