Patchwork [fortran] output of Makefile dependencies

login
register
mail settings
Submitter Tobias Burnus
Date June 27, 2010, 10:25 a.m.
Message ID <4C2726FE.3030501@net-b.de>
Download mbox | patch
Permalink /patch/57089/
State New
Headers show

Comments

Tobias Burnus - June 27, 2010, 10:25 a.m.
Gerald Pfeifer wrote:
> On Sun, 13 Jun 2010, Daniel Franke wrote:
>   
>>>> >>> Can you write something for http://gcc.gnu.org/wiki/Gfortran#news ,
>>>> >>> which will be later moved to the release notes. Best is to also link to
>>>> >>> the manual's -M* options and/or to give an example.
>>>>         
>> > Updated http://gcc.gnu.org/wiki/GFortran#news.
>>     

Which did not work for some reason - thus, I did it myself.

>> > I don't have the wwwdocs checkout, could somebody also update 
>> > http://gcc.gnu.org/gcc-4.6/changes.html?
>>     

I usually wait a while until the changes at the wiki have accumulated
and then commit them to the release notes.

> If you can send me some ("raw") text, I'll be happy to take care of it

Please have a look at the attached diff. Do you have any suggestions or
comments?

Tobias

Patch

Index: changes.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.6/changes.html,v
retrieving revision 1.21
diff -u -r1.21 changes.html
--- changes.html	25 Jun 2010 09:09:14 -0000	1.21
+++ changes.html	27 Jun 2010 09:26:47 -0000
@@ -133,12 +133,20 @@ 
     <li>Much improved compile time for large array constructors.</li>
     <li>Improved diagnostics, especially with
       <code>-fwhole-file</code>.</li>
+    <li>Support the generation of makefile dependencies via the <a
+    href="http://gcc.gnu.org/onlinedocs/gcc/Preprocessor-Options.html">
+    <code>-M</code>...</a> flags of GCC; you might need to specifiy
+    additionally the <code>-cpp</code> option. The dependencies take
+    modules, Fortran's <code>include</code>, and CPP's <code>#include</code>
+    into account. Note: Using <code>-M</code> for the module path is no
+    longer supported, use <code>-J</code> instead.</li>
     <li>Fortran 2003 support has been extended:
       <ul>
         <li>Improved support for polymorphism between libraries and
         programs and for complicated inheritance patterns (cf. <a
         href="http://gcc.gnu.org/wiki/OOP">object-oriented programming</a>).
         </li>
+	<li>Experimental support of the <code>ASSOCIATE</code> construct.</li>
       </ul>
     </li>
     <li>Fortran 2008 support has been extended:
@@ -150,6 +158,17 @@ 
         <code>-fcoarray=single</code></a> flag to enable it.</li>
         <li>The <code>STOP</code> and the new <code>ERROR STOP</code>
         statements now support all constant expressions.</li>
+        <li>Support for the <code>CONTIGUOUS</code> attribute.</li>
+        <li>Support for <code>ALLOCATE</code> with <code>MOLD</code>.</li>
+        <li>Minor changes: obsolesce diagnostics for <code>ENTRY</code> with
+	<code>-std=f2008</code>is obsolescent, a line is permitted to start
+	with a semicolon, for internal and module procedures <code>END</code>
+        can be used besides <code>END SUBROUTINE</code> and <code>END
+        FUNCTION</code>, <code>SELECTED_REAL_KIND</code> now also takes a
+	<code>RADIX</code> argument, intrinsic types are supported for
+	<code>TYPE(<i>intrinsic-type-spec</i>)</code>, multiple type-bound
+        procedures can be declared in a single <code>PROCEDURE</code>
+        statement.</li>
       </ul>
     </li>
   </ul>