[wwwdocs] Update Fortran section in gcc-4.7/changes.html

[Tobias Burnus <tobias dot burnus at physik dot fu-berlin dot de>]

I intent to commit the attached patch soon,
unless you have concerns, comments or suggestions.

Tobias

? changes.diff
Index: changes.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.7/changes.html,v
retrieving revision 1.12
diff -u -r1.12 changes.html
--- changes.html	11 May 2011 16:38:39 -0000	1.12
+++ changes.html	16 May 2011 09:37:44 -0000
@@ -61,6 +61,15 @@
 
 <h3 id="fortran">Fortran</h3>
   <ul>
+    <li>The compile flag <a
+      href="http://gcc.gnu.org/onlinedocs/gfortran/Code-Gen-Options.html#index-g_t_0040code_007bfstack_002darrays_007d-254";
+      ><code>-fstack-arrays</code></a> has been added, which causes
+      that all local arrays are put on stack memory. For some
+      programs this will improve the performance significantly. If your
+      program uses very large local arrays, it is possible that you will
+      have to extend your runtime limits for stack memory.</li>
+    <li>The <code>-Ofast</code> flag now also implies
+      <code>-fno-protect-parens</code> and <code>-fstack-arrays</code>.</li>
     <li>Front-end optimizations can now be selected by the
       <code><a
       href="http://gcc.gnu.org/onlinedocs/gfortran/Code-Gen-Options.html#index-g_t_0040code_007bfrontend_002doptimize_007d-275";
@@ -75,6 +84,29 @@
       href="http://gcc.gnu.org/onlinedocs/gfortran/Code-Gen-Options.html#index-g_t_0040code_007bfaggressive_002dfunction_002delimination_007d-270";>-faggressive-function-elimination</a></code> option
       allows the removal of duplicate function calls even for impure
       functions.</li>
+    <li>The flag <code>-Wreal-q-constant</code> has been added, which
+      warns if floating-point literals have been specified using
+      <code>q</code> (such as <code>1.0q0</code>); the <code>q</code>
+      marker is now supported a vendor extension to denote quad precision
+      (<code>REAL(16)</code> or, if not available, <code>REAL(10)</code>).
+      Consider using a kind parameter (such as in <code>1.0_qp</code>)
+      instead, which can be obtained via <a
+      href="http://gcc.gnu.org/onlinedocs/gfortran/SELECTED_005fREAL_005fKIND.html";
+      ><code>SELECTED_REAL_KIND</code></a>.</li>
+    <li>The <code>GFORTRAN_USE_STDERR</code> environment variable has
+      been removed. GNU Fortran now always prints error messages to
+      standard error. If you wish to redirect standard error, please
+      consult the manual for your OS, shell, batch environment etc.
+      as appropriate.</li> 
+    <li>The <code>-fdump-core</code> option and
+      <code>GFORTRAN_ERROR_DUMPCORE</code> environment variable have
+      been removed. When encountering a serious error, gfortran will
+      now always abort the program. Whether a core dump is generated
+      depends on the user environment settings; see for POSIX shells
+      the <code>ulimit -c</code> and for C shells the <code>limit
+      coredumpsize</code> setting, and see the <a
+      "http://msdn.microsoft.com/en-us/library/bb787181%28v=vs.85%29.aspx";
+      >WER user-mode dumps settings</a> on Windows.</li>
     <li>Fortran 2008:
       <ul>
         <li>The <a href="http://gcc.gnu.org/wiki/Coarray";>coarray</a>
@@ -82,6 +114,15 @@
           MPI-based <a href="http://gcc.gnu.org/wiki/CoarrayLib";>
           coarray communication library</a> has been added.</li>
       </ul></li>
+    <li>TR 29113:
+      <ul>
+        <li>New flag <code>-std=f2008tr</code> permits programs
+          that are expected to conform to the Fortran 2008 standard
+          and the draft technical report (TR) 29113 on Further
+          Interoperability of Fortran with C.</li>
+        <li>The <code>OPTIONAL</code> attribute is now allowed
+          for dummy arguments of <code>BIND(C)</code> procedures.</li> 
+      </ul></li>
   </ul>
 
 <h3>Java (GCJ)</h3>