public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: Qing Zhao <qinzhao@sourceware.org>
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. acd58a986d9d28bc0d9b78caf7317840ee286b73
Date: Fri, 13 Jan 2023 19:47:45 +0000 (GMT)	[thread overview]
Message-ID: <20230113194745.9B8E43858C39@sourceware.org> (raw)

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "gcc-wwwdocs".

The branch, master has been updated
       via  acd58a986d9d28bc0d9b78caf7317840ee286b73 (commit)
      from  e848ac5c5df1c9446bcc8b314c279396533bf0fa (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit acd58a986d9d28bc0d9b78caf7317840ee286b73
Author: Qing Zhao <qing.zhao@oracle.com>
Date:   Fri Jan 13 19:47:01 2023 +0000

    gcc-13/changes: Mention -fstrict-flex-arrays and its impact.

diff --git a/htdocs/gcc-13/changes.html b/htdocs/gcc-13/changes.html
index 41a117b4..96d47903 100644
--- a/htdocs/gcc-13/changes.html
+++ b/htdocs/gcc-13/changes.html
@@ -39,6 +39,10 @@ a work-in-progress.</p>
     <li>Legacy debug info compression option <code>-gz=zlib-gnu</code> was removed
       and the option is ignored right now.</li>
     <li>New debug info compression option value <code>-gz=zstd</code> has been added.</li>
+    <li><code>-Warray-bounds=2</code> will no longer issue warnings for out of
+      bounds accesses to trailing struct members of one-element array type
+      anymore. Instead it diagnoses accesses to trailing arrays according to
+      <code>-fstrict-flex-arrays</code>. </li>
 </ul>
 
 
@@ -434,6 +438,17 @@ a work-in-progress.</p>
 <h2>Other significant improvements</h2>
 
 <!-- <h3 id="uninitialized">Eliminating uninitialized variables</h3> -->
+<h3 id="flexible array">Treating trailing arrays as flexible array members</h3>
+
+<ul>
+ <li>GCC can now control when to treat the trailing array of a structure as a
+     flexible array member for the purpose of accessing the elements of such
+     an array. By default, all trailing arrays in aggregates are treated as
+     flexible array members. Use the new command-line option
+     <code>-fstrict-flex-arrays</code> to control which array members are
+     treated as flexible arrays.
+ </li>
+</ul>
 
 <!-- .................................................................. -->
 <!-- <h2 id="13.1">GCC 13.1</h2> -->

-----------------------------------------------------------------------

Summary of changes:
 htdocs/gcc-13/changes.html | 15 +++++++++++++++
 1 file changed, 15 insertions(+)


hooks/post-receive
-- 
gcc-wwwdocs

                 reply	other threads:[~2023-01-13 19:47 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=20230113194745.9B8E43858C39@sourceware.org \
    --to=qinzhao@sourceware.org \
    --cc=gcc-cvs-wwwdocs@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).