public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <rguenther@suse.de>
To: gcc-patches@gcc.gnu.org
Subject: [PATCH] [www] Move -fstrict-flex-arrays entry
Date: Mon, 17 Apr 2023 11:39:40 +0000 (UTC)	[thread overview]
Message-ID: <nycvar.YFH.7.77.849.2304171139240.4466@jbgna.fhfr.qr> (raw)


Pushed.

The following moves the -fstrict-flex-arrays option mentioning from
"Other significant improvements" to "C family" since the option only
applies there.
---
 htdocs/gcc-13/changes.html | 18 +++++++-----------
 1 file changed, 7 insertions(+), 11 deletions(-)

diff --git a/htdocs/gcc-13/changes.html b/htdocs/gcc-13/changes.html
index 84207104..f3b9afed 100644
--- a/htdocs/gcc-13/changes.html
+++ b/htdocs/gcc-13/changes.html
@@ -195,6 +195,13 @@ a work-in-progress.</p>
       assumptions support also in C or older C++:
       <a href="https://gcc.gnu.org/onlinedocs/gcc/Statement-Attributes.html#index-assume-statement-attribute"><code>__attribute__((assume(EXPR)));</code></a>
   </li>
+ <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
+     <a href="https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html#index-Wstrict-flex-arrays"><code>-fstrict-flex-arrays</code></a>
+     to control which array members are treated as flexible arrays.
+ </li>
 </ul>
 
 <h3 id="c">C</h3>
@@ -708,17 +715,6 @@ a work-in-progress.</p>
 <h2>Other significant improvements</h2>
 
 <!-- <h3 id="uninitialized">Eliminating uninitialized variables</h3> -->
-<h3 id="flexible-arrays">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
-     <a href="https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html#index-Wstrict-flex-arrays"><code>-fstrict-flex-arrays</code></a>
-     to control which array members are treated as flexible arrays.
- </li>
-</ul>
 
 <!-- .................................................................. -->
 <!-- <h2 id="13.1">GCC 13.1</h2> -->
-- 
2.35.3

                 reply	other threads:[~2023-04-17 11:39 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=nycvar.YFH.7.77.849.2304171139240.4466@jbgna.fhfr.qr \
    --to=rguenther@suse.de \
    --cc=gcc-patches@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).