Small tweak to documentation of scalar_storage_order
gcc/ PR c/100653 * doc/extend.texi (scalar_storage_order): Rephrase slightly.
This commit is contained in:
parent
abe8787a84
commit
58523f23fe
1 changed files with 3 additions and 2 deletions
|
@ -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
|
||||
|
|
Loading…
Add table
Reference in a new issue