public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Sandra Loosemore <sandra@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r13-6642] Docs: Fix double 'See' in zero-length-bounds docs. Date: Mon, 13 Mar 2023 19:50:55 +0000 (GMT) [thread overview] Message-ID: <20230313195055.057FE3858D1E@sourceware.org> (raw) https://gcc.gnu.org/g:8e9c65d34c799c9dadea1e2e60b4180f26262829 commit r13-6642-g8e9c65d34c799c9dadea1e2e60b4180f26262829 Author: Sean Bright <sean@seanbright.com> Date: Mon Mar 13 19:49:22 2023 +0000 Docs: Fix double 'See' in zero-length-bounds docs. gcc/ChangeLog: * doc/invoke.texi (Warning Options): Remove errant 'See' before @xref. Diff: --- gcc/doc/invoke.texi | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi index 8d71d3d6ea5..8adcddb7a19 100644 --- a/gcc/doc/invoke.texi +++ b/gcc/doc/invoke.texi @@ -8345,7 +8345,7 @@ conversions the warnings @option{-Wno-int-to-pointer-cast} and @item -Wzero-length-bounds Warn about accesses to elements of zero-length array members that might overlap other members of the same object. Declaring interior zero-length -arrays is discouraged because accesses to them are undefined. See +arrays is discouraged because accesses to them are undefined. @xref{Zero Length}. For example, the first two stores in function @code{bad} are diagnosed
reply other threads:[~2023-03-13 19:50 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=20230313195055.057FE3858D1E@sourceware.org \ --to=sandra@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: 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).