From: Gerald Pfeifer <gerald@pfeifer.com>
To: Thomas Preudhomme <thomas.preudhomme@foss.arm.com>
Cc: NightStrike <nightstrike@gmail.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
JonY <10walls@gmail.com>
Subject: [wwwdocs] gcc-8/porting_to.html (was: [PATCH, GCC/x86 mingw32] Add configure option to force wildcard behavior on Windows)
Date: Sat, 04 Mar 2017 14:25:00 -0000 [thread overview]
Message-ID: <alpine.LSU.2.20.1703041520500.2487@anthias.pfeifer.com> (raw)
In-Reply-To: <a9e302fb-b796-0f33-6c6d-c20ca2b6e502@foss.arm.com>
On Thu, 2 Mar 2017, Thomas Preudhomme wrote:
>> This should be mentioned in the "porting to" page when it eventually
>> goes in, as it may be surprising behavior.
> Will do once the file is created for gcc-8. Thanks for the suggestion
Here we go. :-) Applied.
Gerald
Index: porting_to.html
===================================================================
RCS file: porting_to.html
diff -N porting_to.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ porting_to.html 4 Mar 2017 14:20:46 -0000
@@ -0,0 +1,37 @@
+<html>
+
+<head>
+<title>Porting to GCC 8</title>
+</head>
+
+<body>
+<h1>Porting to GCC 8</h1>
+
+<p>
+The GCC 8 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.
+</p>
+
+<p>
+Some of these changes are user visible and can cause grief when
+porting to GCC 8. This document is an effort to identify common issues
+and provide solutions. Let us know if you have suggestions for improvements!
+</p>
+
+
+<h2 id="cpp">Preprocessor issues</h2>
+
+
+<h2 id="c">C language issues</h2>
+
+
+<h2 id="cxx">C++ language issues</h2>
+
+
+<h2 id="links">Links</h2>
+
+</body>
+</html>
next prev parent reply other threads:[~2017-03-04 14:25 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-18 9:49 [PATCH, GCC/x86 mingw32] Add configure option to force wildcard behavior on Windows Thomas Preudhomme
2017-01-19 2:05 ` JonY
2017-01-20 9:06 ` Thomas Preudhomme
2017-01-26 13:19 ` Thomas Preudhomme
2017-02-07 8:48 ` JonY
2017-02-14 9:46 ` Thomas Preudhomme
2017-02-14 10:58 ` JonY
2017-02-17 11:01 ` JonY
2017-02-17 11:51 ` Thomas Preudhomme
2017-02-17 23:05 ` JonY
2017-02-22 16:07 ` Thomas Preudhomme
[not found] ` <CAF1jjLtsw10najrRwzJ7MJSSKxqmX0Wy4gKyf=dhmcAebS+JOA@mail.gmail.com>
2017-03-02 16:58 ` Thomas Preudhomme
2017-03-04 14:25 ` Gerald Pfeifer [this message]
2017-03-09 10:51 ` [wwwdocs] gcc-8/porting_to.html Thomas Preudhomme
2017-03-09 10:59 ` Jakub Jelinek
2017-03-09 11:22 ` Thomas Preudhomme
2017-03-09 13:16 ` JonY
2017-03-12 14:08 ` Gerald Pfeifer
2017-03-12 23:51 ` JonY
2017-03-22 17:39 ` Thomas Preudhomme
2017-03-22 22:51 ` JonY
2017-03-23 6:47 ` Gerald Pfeifer
2017-03-23 10:47 ` Thomas Preudhomme
2017-05-04 11:10 ` JonY
2017-05-04 14:37 ` Thomas Preudhomme
2017-05-04 14:43 ` Thomas Preudhomme
2017-05-04 15:17 ` [arm-embedded] [PATCH, GCC/x86 mingw32] Add configure option to force wildcard behavior on Windows Thomas Preudhomme
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=alpine.LSU.2.20.1703041520500.2487@anthias.pfeifer.com \
--to=gerald@pfeifer.com \
--cc=10walls@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=nightstrike@gmail.com \
--cc=thomas.preudhomme@foss.arm.com \
/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: 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).