aboutsummaryrefslogtreecommitdiff
path: root/gcc/doc
diff options
context:
space:
mode:
authorEric Botcazou <ebotcazou@adacore.com>2021-05-27 00:24:20 +0200
committerEric Botcazou <ebotcazou@adacore.com>2021-05-27 00:25:26 +0200
commit58523f23fefcef0850841e7055d75d4309f0453e (patch)
tree0b62de95840cfc3c9ff01a91f3cb58f9f1ca3a8e /gcc/doc
parentabe8787a8492013145b275b858f70943522d7226 (diff)
downloadgcc-58523f23fefcef0850841e7055d75d4309f0453e.zip
gcc-58523f23fefcef0850841e7055d75d4309f0453e.tar.gz
gcc-58523f23fefcef0850841e7055d75d4309f0453e.tar.bz2
Small tweak to documentation of scalar_storage_order
gcc/ PR c/100653 * doc/extend.texi (scalar_storage_order): Rephrase slightly.
Diffstat (limited to 'gcc/doc')
-rw-r--r--gcc/doc/extend.texi5
1 files changed, 3 insertions, 2 deletions
diff --git a/gcc/doc/extend.texi b/gcc/doc/extend.texi
index 3ddeb0d..bfe9c21 100644
--- 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