public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Richard Biener <rguenth@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. c06f4956bbcb13837e52f58cadf07379645b0399 Date: Mon, 17 Apr 2023 11:39:50 +0000 (GMT) [thread overview] Message-ID: <20230417113950.BB85C3858C2F@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 c06f4956bbcb13837e52f58cadf07379645b0399 (commit) from c64a22493359c02392aed483d514c6d3a28832c4 (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 c06f4956bbcb13837e52f58cadf07379645b0399 Author: Richard Biener <rguenther@suse.de> Date: Mon Apr 17 13:37:22 2023 +0200 [www] Move -fstrict-flex-arrays entry The following moves the -fstrict-flex-arrays option mentioning from "Other significant improvements" to "C family" since the option only applies there. 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> --> ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-13/changes.html | 18 +++++++----------- 1 file changed, 7 insertions(+), 11 deletions(-) hooks/post-receive -- gcc-wwwdocs
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=20230417113950.BB85C3858C2F@sourceware.org \ --to=rguenth@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: linkBe 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).