public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Eric Botcazou <ebotcazou@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r12-1083] Small tweak to documentation of scalar_storage_order
Date: Wed, 26 May 2021 22:26:07 +0000 (GMT)	[thread overview]
Message-ID: <20210526222607.151A53847821@sourceware.org> (raw)

https://gcc.gnu.org/g:58523f23fefcef0850841e7055d75d4309f0453e

commit r12-1083-g58523f23fefcef0850841e7055d75d4309f0453e
Author: Eric Botcazou <ebotcazou@adacore.com>
Date:   Thu May 27 00:24:20 2021 +0200

    Small tweak to documentation of scalar_storage_order
    
    gcc/
            PR c/100653
            * doc/extend.texi (scalar_storage_order): Rephrase slightly.

Diff:
---
 gcc/doc/extend.texi | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/gcc/doc/extend.texi b/gcc/doc/extend.texi
index 3ddeb0dee3a..bfe9c21bddf 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


                 reply	other threads:[~2021-05-26 22:26 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210526222607.151A53847821@sourceware.org \
    --to=ebotcazou@gcc.gnu.org \
    --cc=gcc-cvs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).