public inbox for
help / color / mirror / Atom feed
From: Andrew Pinski <>
Subject: gcc-wwwdocs branch master updated. 4405fd98dff55185e7ca3ca43e8ab108985d2bb2
Date: Wed, 29 Sep 2021 08:53:00 +0000 (GMT)	[thread overview]
Message-ID: <> (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  4405fd98dff55185e7ca3ca43e8ab108985d2bb2 (commit)
      from  158eee20b5257e9b3d0654f5fe10e60d1741bebe (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 4405fd98dff55185e7ca3ca43e8ab108985d2bb2
Author: Andrew Pinski <>
Date:   Wed Sep 29 00:30:57 2021 +0000

    [www] Add note about computed gotos to changes and porting guide
    Even though there is not many computed gotos in the wild and even less
    that would use an integer type, it would still be a good idea to add
    this new error message to both changes and the porting to guide.

diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html
index 1f156a9a..31307107 100644
--- a/htdocs/gcc-12/changes.html
+++ b/htdocs/gcc-12/changes.html
@@ -17,11 +17,9 @@
 This page is a "brief" summary of some of the huge number of improvements
 in GCC 12.
 You may also want to check out our
 <a href="porting_to.html">Porting to GCC 12</a> page and the
 <a href="../onlinedocs/index.html#current">full GCC documentation</a>.
 <p>Note: GCC 12 has not been released yet, so this document is
@@ -30,6 +28,10 @@ a work-in-progress.</p>
 <!-- .................................................................. -->
+  <li>
+    <strong>C:</strong>
+    Computed gotos require a pointer type now.
+  </li>
     Two non-standard <code>std::pair</code> constructors have been deprecated.
diff --git a/htdocs/gcc-12/porting_to.html b/htdocs/gcc-12/porting_to.html
new file mode 100644
index 00000000..9154d7b3
--- /dev/null
+++ b/htdocs/gcc-12/porting_to.html
@@ -0,0 +1,66 @@
+<!DOCTYPE html>
+<html lang="en">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<title>Porting to GCC 12</title>
+<link rel="stylesheet" type="text/css" href="" />
+<h1>Porting to GCC 12</h1>
+The GCC 12 release series differs from previous GCC releases in
+<a href="changes.html">a number of ways</a>. Some of these are a result
+of bug fixing, and some old behaviors have been intentionally changed
+to support new standards, or relaxed in standards-conforming ways to
+facilitate compilation or run-time performance.
+Some of these changes are user visible and can cause grief when
+porting to GCC 12. This document is an effort to identify common issues
+and provide solutions. Let us know if you have suggestions for improvements!
+<h2 id="cpp">Preprocessor issues</h2>
+<h2 id="c">C language issues</h2>
+<h3 id="computedgotos">Computed goto now require a pointer type</h3>
+In GCC 12, computed gotos require a pointer type.
+An example which was accepted before:</p>
+  void f(void)
+  {
+    goto *10;
+  }
+is no longer accepted and you need to add a cast to it like:
+  void f(void)
+  {
+    goto *(void*)10;
+  }
+<h2 id="cxx">C++ language issues</h2>
+<h2 id="fortran">Fortran language issues</h2>
+<h2 id="links">Links</h2>


Summary of changes:
 htdocs/gcc-12/changes.html    |  6 ++--
 htdocs/gcc-12/porting_to.html | 66 +++++++++++++++++++++++++++++++++++++++++++
 2 files changed, 70 insertions(+), 2 deletions(-)
 create mode 100644 htdocs/gcc-12/porting_to.html


                 reply	other threads:[~2021-09-29  8:53 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).