[wwwdocs] Couple of items for gcc-8/changes.html

Message ID 1526216.WeHouzEXq0@polaris
State New
Headers show
Series
  • [wwwdocs] Couple of items for gcc-8/changes.html
Related show

Commit Message

Eric Botcazou March 21, 2018, 8:44 a.m.
Plus a wording change for the sake of consistency.  OK to commit?

-- 
Eric Botcazou

Comments

Gerald Pfeifer April 1, 2018, 9:22 p.m. | #1
On Wed, 21 Mar 2018, Eric Botcazou wrote:
> Plus a wording change for the sake of consistency.  OK to commit?


Yes, thank you, Eric.

Gerald

Patch

Index: htdocs/gcc-8/changes.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-8/changes.html,v
retrieving revision 1.47
diff -u -r1.47 changes.html
--- htdocs/gcc-8/changes.html	20 Mar 2018 08:22:03 -0000	1.47
+++ htdocs/gcc-8/changes.html	21 Mar 2018 08:42:39 -0000
@@ -30,8 +30,7 @@ 
   <li>Support for the obsolete SDB/coff debug info format has been
       <strong>removed</strong>.  The option <code>-gcoff</code> no longer
       does anything.</li>
-  <li>The Cilk+ extensions to the C and C++ languages were removed from
-      GCC.</li>
+  <li>The Cilk+ extensions to the C and C++ languages have been removed.</li>
   <li>
     The MPX extensions to the C and C++ languages have been deprecated and
     will be removed in a future release.
@@ -103,6 +102,11 @@ 
     thus mitigate the attack vector that relies on jumping over
     a stack guard page as provided by the operating system.
   </li>
+  <li>
+    A new pragma <code>GCC unroll</code> has been implemented in the C
+    family of languages, as well as Fortran and Ada, so as to make it
+    possible for the user to have a finer-grained control over the loop
+    unrolling optimization than with optimization switches.
 </ul>
 
 
@@ -111,7 +115,11 @@ 
 
 <h3 id="ada">Ada</h3>
 <ul>
-  <li></li>
+  <li>For its internal exception handling used on the host for error
+      recovery in the front-end, the compiler now relies on the native
+      exception handling mechanism of the host platform, which should
+      be more efficient than the former mechanism.
+  </li>
 </ul>
 
 <h3 id="brig">BRIG (HSAIL)</h3>