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>
