[wwwdocs, patch] gcc-4.9/changes.html: Add quip about "#pragma GCC ivdep" and update Fortran section

[Tobias Burnus]

Dear Gerald, dear all,

the patch adds a quip about the new "#pragma GCC ivdep" to the release 
notes. Additionally, I updated the Fortran section based on the changes 
accumulated on http://gcc.gnu.org/wiki/GFortran#news

Any comments? Or is the patch OK?

Tobias
Index: htdocs/gcc-4.9/changes.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.9/changes.html,v
retrieving revision 1.28
diff -u -p -r1.28 changes.html
--- htdocs/gcc-4.9/changes.html	3 Oct 2013 14:15:36 -0000	1.28
+++ htdocs/gcc-4.9/changes.html	24 Oct 2013 19:44:28 -0000
@@ -84,6 +84,13 @@
 
     <b>test.C:2:46:</b> <b style='color:red'>error:</b> incomplete type &lsquo;<b>X&lt;100&gt;</b>&rsquo; used in nested name specifier
     </pre></li>
+
+    <li>With the new <a
+    href="http://gcc.gnu.org/onlinedocs/gcc/Loop_002dSpecific-Pragmas.html";
+    ><code>#pragma GCC ivdep</code></a>, the user can assert that there are no
+    loop-carried dependencies which would prevent that consecutive iterations of
+    the following loop can be executed concurrently with SIMD (single instruction
+    multiple data) instructions.</li>
   </ul>           
 
 <!--
@@ -173,13 +180,18 @@ void f(int n) {
           trying to mix old code with new code will usually give an error
           message.)</li>
       </ul></li>
+      <li>GNU Fortran no longer deallocates allocatable variables or
+        allocatable components of variables declared in the main program. The
+        Fortran standard states since 2008 explicitly that variables declared
+        in the Fortran main program automatically have the <code>SAVE</code>
+        attribute.</li>
     </ul></li>
     <li>The deprecated command-line option <code>-fno-whole-file</code>
       has been removed. (<code>-fwhole-file</code> is the default since
       GCC 4.6.) <code>-fwhole-file</code>/<code>-fno-whole-file</code>
       continue to be accepted but do not influence the code generation.</li>
     <li>The compiler no longer unconditionally warns
-      about <code>DO</code>loops with zero iterations.  This warning is now
+      about <code>DO</code> loops with zero iterations.  This warning is now
       controlled by the <code>-Wzerotrips</code> option, which is implied by
       <code>-Wall</code>.</li>
     <li>The new <code>NO_ARG_CHECK</code> attribute of the <a