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. daec8707932f2049a4834166a93ca9cc7fe19224 Date: Thu, 3 Aug 2023 13:59:34 +0000 (GMT) [thread overview] Message-ID: <20230803135934.9167D3858D1E@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 daec8707932f2049a4834166a93ca9cc7fe19224 (commit) from 5b9a2f102647fd26ac63f483e1d54377f956ce7e (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 daec8707932f2049a4834166a93ca9cc7fe19224 Author: Qing Zhao <qing.zhao@oracle.com> Date: Thu Aug 3 13:59:21 2023 +0000 gcc-13/changes.html: Add and fix URL to -fstrict-flex-array option. diff --git a/htdocs/gcc-13/changes.html b/htdocs/gcc-13/changes.html index c1486563..10c54689 100644 --- a/htdocs/gcc-13/changes.html +++ b/htdocs/gcc-13/changes.html @@ -46,7 +46,7 @@ You may also want to check out our 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> + <a href="https://gcc.gnu.org/onlinedocs/gcc-13.1.0/gcc/C-Dialect-Options.html#index-fstrict-flex-arrays"><code>-fstrict-flex-arrays</code></a>. </li> <li><a href="https://gcc.gnu.org/onlinedocs/gcc-13.1.0/gcc/Static-Analyzer-Options.html"><code>-fanalyzer</code></a> is still only suitable for analyzing C code. In particular, using it on C++ is unlikely to give meaningful output.</li> @@ -213,7 +213,7 @@ You may also want to check out our 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-13.1.0/gcc/Warning-Options.html#index-Wstrict-flex-arrays"><code>-fstrict-flex-arrays</code></a> + <a href="https://gcc.gnu.org/onlinedocs/gcc-13.1.0/gcc/C-Dialect-Options.html#index-fstrict-flex-arrays"><code>-fstrict-flex-arrays</code></a> to control which array members are treated as flexible arrays. </li> </ul> ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-13/changes.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2023-08-03 13:59 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=20230803135934.9167D3858D1E@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: 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).