public inbox for
help / color / mirror / Atom feed
From: Martin Liska <>
Subject: gcc-wwwdocs branch master updated. b89dff3305518093bc2cbfce6f5bb4845992b88b
Date: Tue, 24 May 2022 12:00:46 +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  b89dff3305518093bc2cbfce6f5bb4845992b88b (commit)
      from  cf90f8a4e0666dc3a23ae2bc9de801e9a897ac46 (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 b89dff3305518093bc2cbfce6f5bb4845992b88b
Author: Martin Liska <>
Date:   Tue May 24 13:59:39 2022 +0200

    GCC 13: come up with Porting to.
    And link it from changes.html.

diff --git a/htdocs/gcc-13/changes.html b/htdocs/gcc-13/changes.html
index 2d974ae5..6c5b2a37 100644
--- a/htdocs/gcc-13/changes.html
+++ b/htdocs/gcc-13/changes.html
@@ -17,11 +17,9 @@
 This page is a "brief" summary of some of the huge number of improvements
 in GCC 13.
 You may also want to check out our
 <a href="porting_to.html">Porting to GCC 13</a> page and the
 <a href="../onlinedocs/index.html#current">full GCC documentation</a>.
 <p>Note: GCC 13 has not been released yet, so this document is
diff --git a/htdocs/gcc-13/porting_to.html b/htdocs/gcc-13/porting_to.html
new file mode 100644
index 00000000..b3e0895a
--- /dev/null
+++ b/htdocs/gcc-13/porting_to.html
@@ -0,0 +1,28 @@
+<!DOCTYPE html>
+<html lang="en">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<title>Porting to GCC 13</title>
+<link rel="stylesheet" type="text/css" href="" />
+<h1>Porting to GCC 13</h1>
+The GCC 13 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 13. This document is an effort to identify common issues
+and provide solutions. Let us know if you have suggestions for improvements!


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


                 reply	other threads:[~2022-05-24 12:00 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).