public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Jonathan Wakely <redi@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 5f199e1197b67b4304a3be54579c2141c39bff30 Date: Tue, 1 Feb 2022 12:54:49 +0000 (GMT) [thread overview] Message-ID: <20220201125449.B7240385C403@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 5f199e1197b67b4304a3be54579c2141c39bff30 (commit) from 9f6040a13e7c552a8c1c65352b702dc5d71b369e (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 5f199e1197b67b4304a3be54579c2141c39bff30 Author: Jonathan Wakely <jwakely@redhat.com> Date: Tue Feb 1 12:54:42 2022 +0000 Fix grammar for computed goto notes diff --git a/htdocs/gcc-12/porting_to.html b/htdocs/gcc-12/porting_to.html index 86d99723..7f4a2936 100644 --- a/htdocs/gcc-12/porting_to.html +++ b/htdocs/gcc-12/porting_to.html @@ -30,10 +30,10 @@ and provide solutions. Let us know if you have suggestions for improvements! --> <h2 id="c">C language issues</h2> -<h3 id="computedgotos">Computed goto now require a pointer type</h3> +<h3 id="computedgotos">Computed goto now requires a pointer type</h3> <p> -In GCC 12, computed gotos require a pointer type. +In GCC 12, a computed goto requires a pointer type. An example which was accepted before:</p> <pre><code> void f(void) ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-12/porting_to.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2022-02-01 12:54 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=20220201125449.B7240385C403@sourceware.org \ --to=redi@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).