This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
[committed, Fortran] PR67039 and PR58000 minor documentation changes
- From: Dominique d'HumiÃres <dominiq at lps dot ens dot fr>
- To: fortran at gcc dot gnu dot org
- Cc: Jerry DeLisle <jvdelisle at charter dot net>, gcc-patches <gcc-patches at gcc dot gnu dot org>
- Date: Wed, 13 Apr 2016 17:14:49 +0200
- Subject: [committed, Fortran] PR67039 and PR58000 minor documentation changes
- Authentication-results: sourceware.org; auth=none
I have committed the following patches to trunk after Jerryâs approval on bugzilla. Is it OK to back port them to the gcc-5 branch?
Dominique
Index: gcc/fortran/ChangeLog
===================================================================
--- gcc/fortran/ChangeLog (revision 234935)
+++ gcc/fortran/ChangeLog (working copy)
@@ -1,3 +1,9 @@
+2016-04-13 Dominique d'Humieres <dominiq@lps.ens.fr>
+
+ PR fortran/58000
+ * gfortran.texi: Document OPEN( ... NAME=) as not implemented
+ in GNU Fortran
+
2016-04-09 Jerry DeLisle <jvdelisle@gcc.gnu.org>
PR fortran/68566
Index: gcc/fortran/gfortran.texi
===================================================================
--- gcc/fortran/gfortran.texi (revision 234935)
+++ gcc/fortran/gfortran.texi (working copy)
@@ -2148,6 +2148,7 @@
@c * Omitted arguments in procedure call::
* Alternate complex function syntax::
* Volatile COMMON blocks::
+* OPEN( ... NAME=)::
@end menu
@@ -2355,7 +2356,20 @@
+@node OPEN( ... NAME=)
+@subsection @code{OPEN( ... NAME=)}
+@cindex @code{NAM}
+
+Some Fortran compilers, including @command{g77}, let the user declare
+@code{OPEN( ... NAME=)}. This is
+invalid standard Fortran syntax and is not supported by
+@command{gfortran}. @code{OPEN( ... NAME=)} should be replaced
+with @code{OPEN( ... FILE=)}.
+
+
+
@c ---------------------------------------------------------------------
+@c ---------------------------------------------------------------------
@c Mixed-Language Programming
@c ââââââââââââââââââââââââââââââââââ
Index: gcc/fortran/ChangeLog
===================================================================
--- gcc/fortran/ChangeLog (revision 234942)
+++ gcc/fortran/ChangeLog (working copy)
@@ -1,5 +1,11 @@
+2016-04-13 Dominique d'Humieres <dominiq@lps.ens.fr>
+
+ PR fortran/67039
+ * intrinsic.texi: Correct the documentation of pseudorandom
+ number intrinsics.
+
2016-04-13 Dominique d'Humieres <dominiq@lps.ens.fr>
PR fortran/58000
* gfortran.texi: Document OPEN( ... NAME=) as not implemented
in GNU Fortran
Index: gcc/fortran/intrinsic.texi
===================================================================
--- gcc/fortran/intrinsic.texi (revision 234942)
+++ gcc/fortran/intrinsic.texi (working copy)
@@ -12628,10 +12628,12 @@
See @code{RAND} and @code{IRAND} for examples.
@item @emph{Notes}:
-The Fortran 2003 standard specifies the intrinsic @code{RANDOM_SEED} to
-initialize the pseudo-random numbers generator and @code{RANDOM_NUMBER}
-to generate pseudo-random numbers. Please note that in
-GNU Fortran, these two sets of intrinsics (@code{RAND},
+The Fortran standard specifies the intrinsic subroutines
+@code{RANDOM_SEED} to initialize the pseudo-random number
+generator and @code{RANDOM_NUMBER} to generate pseudo-random numbers.
+These subroutines should be used in new codes.
+
+Please note that in GNU Fortran, these two sets of intrinsics (@code{RAND},
@code{IRAND} and @code{SRAND} on the one hand, @code{RANDOM_NUMBER} and
@code{RANDOM_SEED} on the other hand) access two independent
pseudo-random number generators.