diff mbox

[wwwdocs] Add "Porting to GCC 4.9" document

Message ID alpine.LSU.2.11.1408312121000.5181@tuna.site
State New
Headers show

Commit Message

Gerald Pfeifer Aug. 31, 2014, 7:23 p.m. UTC
On Tue, 4 Mar 2014, Jonathan Wakely wrote:
> I've added an initial "Porting to GCC 4.9" page at
> http://gcc.gnu.org/gcc-4.9/porting_to.html

Very nice!  Thank you for doing this.

What do you think about the following patch with minor changes?

The only material one (apart from making the URL relative, is
there any problem with that?) is that I'm toning down the language
in how disruptive this release is.  Compared to releases around
GCC 4.4 this looks like a very harmless one. :-)

Gerald

Comments

Jonathan Wakely Aug. 31, 2014, 7:28 p.m. UTC | #1
On 31/08/14 21:23 +0200, Gerald Pfeifer wrote:
>On Tue, 4 Mar 2014, Jonathan Wakely wrote:
>>I've added an initial "Porting to GCC 4.9" page at
>>http://gcc.gnu.org/gcc-4.9/porting_to.html
>
>Very nice!  Thank you for doing this.
>
>What do you think about the following patch with minor changes?
>
>The only material one (apart from making the URL relative, is
>there any problem with that?) is that I'm toning down the language
>in how disruptive this release is.  Compared to releases around
>GCC 4.4 this looks like a very harmless one. :-)

I just copied that text from previous porting_to.html pages, your
changes look good to me.
diff mbox

Patch

Index: porting_to.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.9/porting_to.html,v
retrieving revision 1.6
diff -u -r1.6 porting_to.html
--- porting_to.html	11 Jun 2014 18:49:26 -0000	1.6
+++ porting_to.html	31 Aug 2014 19:20:52 -0000
@@ -8,12 +8,11 @@ 
 <h1>Porting to GCC 4.9</h1>
 
 <p>
-The GCC 4.9 release series differs from previous GCC releases in more
-than the usual list of
-<a href="https://gcc.gnu.org/gcc-4.9/changes.html">changes</a>. Some of
+The GCC 4.9 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 in order to support new standards, or relaxed
-in standards-conforming ways to facilitate compilation or runtime
+in standards-conforming ways to facilitate compilation or run-time
 performance.  Some of these changes are not visible to the naked eye
 and will not cause problems when updating from older versions.
 </p>
@@ -35,7 +34,7 @@ 
 
 <h2>C/C++ language issues</h2>
 
-<h3>Invalid OpenMP #pragma omp end directive now diagnosed</h3>
+<h3>Invalid OpenMP <code>#pragma omp end</code> directive now diagnosed</h3>
 
 <p> GCC no longer accepts invalid OpenMP like: </p>
 
@@ -90,6 +89,7 @@ 
 <p>This optimization can also affect implicit null pointer checks such as
 the one done by the C++ runtime for the <code>delete[]</code> operator.</p>
 
+
 <h2>C language issues</h2>
 
 <h3>Right operand of comma operator without effect</h3>
@@ -117,6 +117,7 @@ 
   bar (), (void) i;
 </code></pre>
 
+
 <h2>C++ language issues</h2>
 
 <h3>Shadowing name of exception in <code>catch</code> handler now rejected</h3>
@@ -208,6 +209,7 @@ 
    using ::max_align_t;
            <b style='color:lime'>^</b>
 </pre>
+
 <p>Another possible error is:</p>
 <pre>
 <b>someheader.h:99:13:</b> <b style='color:red'>error:</b> &lsquo;<b>ptrdiff_t</b>&rsquo; does not name a type
@@ -237,4 +239,3 @@ 
 
 </body>
 </html>
-