bugs.texi, [...]: Doc updates from Craig.

        * bugs.texi, g77.1, g77.texi, intdoc.in, news.texi: Doc updates
        from Craig.

From-SVN: r22153

diff --git a/gcc/f/bugs.texi b/gcc/f/bugs.texi
index 436caa49b94978646aa29052083d77b2d5489be3..af18d80cdbce29c2134f9f820f46a86b2d1a2249 100644 (file)
--- a/gcc/f/bugs.texi
+++ b/gcc/f/bugs.texi
@@ -5,7 +5,7 @@
 @c The text of this file appears in the file BUGS
 @c in the G77 distribution, as well as in the G77 manual.
 
-@c 1998-07-15
+@c 1998-09-01
 
 @ifclear BUGSONLY
 @node Actual Bugs
@@ -72,6 +72,13 @@ and @code{ASSIGN} are involved.
 
 Fixed in @code{egcs} version 1.1.
 
+@item
+@code{g77} fails to warn about
+use of a ``live'' iterative-DO variable
+as an implied-DO variable
+in a @samp{WRITE} or @samp{PRINT} statement
+(although it does warn about this in a @samp{READ} statement).
+
 @item
 A compiler crash, or apparently infinite run time,
 can result when compiling complicated expressions
@@ -231,17 +238,13 @@ by versions of @code{g77} prior to 0.5.20.
 @cindex -fPIC option
 @cindex options, -fPIC
 @item
-There seem to be some problems with passing constants, and perhaps
-general expressions (other than simple variables/arrays), to procedures
-when compiling on some systems (such as i386) with @samp{-fPIC}, as in
-when compiling for ELF targets.
+@code{g77} sometimes produces invalid assembler code
+when using the @samp{-fPIC} option (such as compiling for ELF targets)
+on the Intel x86 architecture target.
 The symptom is that the assembler complains about invalid opcodes.
-This bug is in the gcc back end,
-and it apparently occurs only when
-compiling sufficiently complicated functions @emph{without} the
-@samp{-O} option.
+This bug is in the gcc back end.
 
-Fixed in @code{egcs} version 1.1.
+Fixed in @code{egcs} version 1.0.2.
 
 @cindex padding
 @cindex structures

diff --git a/gcc/f/g77.1 b/gcc/f/g77.1
index 3a8504dd6108213a23bc5dcab06e263ff054621b..d6a465b07eabd08ad8b5afc4b95e8718ce2a45fd 100644 (file)
--- a/gcc/f/g77.1
+++ b/gcc/f/g77.1
@@ -1,20 +1,20 @@
 .\" Copyright (c) 1995-1997 Free Software Foundation              -*-Text-*-
 .\" See section COPYING for conditions for redistribution
 .\" FIXME: no info here on predefines.  Should there be?  extra for F77...
-.TH G77 1 "1998-04-17" "GNU Tools" "GNU Tools"
+.TH G77 1 "1998-09-01" "GNU Tools" "GNU Tools"
 .de BP
 .sp
 .ti \-.2i
 \(**
 ..
 .SH NAME
-g77 \- GNU project Fortran Compiler (v0.5.23)
+g77 \- GNU project Fortran Compiler (v0.5.24)
 .SH SYNOPSIS
 .RB g77 " [" \c
 .IR option " | " "filename " ].\|.\|.
 .SH WARNING
 The information in this man page is an extract from the full
-documentation of the GNU Fortran compiler (version 0.5.23),
+documentation of the GNU Fortran compiler (version 0.5.24),
 and is limited to the meaning of some of the options.
 .PP
 This man page is not up to date, since no volunteers want to
@@ -22,8 +22,8 @@ maintain it.  If you find a discrepancy between the man page and the
 software, please check the Info file, which is the authoritative
 documentation.
 .\" .PP
-.\" The version of GNU Fortran documented by the Info file is 0.5.23,
-.\" which includes substantial improvements and changes since 0.5.23,
+.\" The version of GNU Fortran documented by the Info file is 0.5.24,
+.\" which includes substantial improvements and changes since 0.5.24,
 .\" the version documented in this man page.
 .PP
 If we find that the things in this man page that are out of date cause
@@ -37,7 +37,7 @@ For complete and current documentation, refer to the Info file `\|\c
 .B g77\c
 \&\|' or the manual
 .I
-Using and Porting GNU Fortran (for version 0.5.23)\c
+Using and Porting GNU Fortran (for version 0.5.24)\c
 \&.  Both are made from the Texinfo source file
 .BR g77.texi .
 .PP
@@ -268,7 +268,7 @@ a.out     link edited output
 .br
 \fILIBDIR\fR/f771      compiler
 .br
-\fILIBDIR\fR/libf2c.a  Fortran run-time library
+\fILIBDIR\fR/libg2c.a  Fortran run-time library
 .br
 \fILIBDIR\fR/libgcc.a  GCC subroutine library
 .br
@@ -311,7 +311,7 @@ entries in
 \&.
 .br
 .I
-Using and Porting GNU Fortran (for version 0.5.23)\c
+Using and Porting GNU Fortran (for version 0.5.24)\c
 , James Craig Burley;
 .I
 Using and Porting GNU CC (for version 2.0)\c

diff --git a/gcc/f/intdoc.in b/gcc/f/intdoc.in
index d7a85a01befb81d7907da1ba5b27783dc65af45e..62b93645b1e41499b4c5bda29216bee166fe0694 100644 (file)
--- a/gcc/f/intdoc.in
+++ b/gcc/f/intdoc.in
@@ -2058,9 +2058,10 @@ Fills @var{@1@} with the system's host name returned by
 @code{gethostname(2)}, returning 0 on success or a non-zero error code
 (@code{ENOSYS} if the system does not provide @code{gethostname(2)}).
 
-On some systems (specifically SCO) it might be necessary to link the
-``socket'' library if you call this routine, i.e.@: append
-@samp{-lg2c -lsocket -lm} to the @code{g77} arguments.
+On some systems (specifically SCO) it may be necessary to link the
+``socket'' library if you call this routine.
+Typically this means adding @samp{-lg2c -lsocket -lm}
+to the @code{g77} command line when linking the program.
 ")
 
 DEFDOC (HOSTNM_subr, "Get host name.", "\
@@ -2074,9 +2075,10 @@ Some non-GNU implementations of Fortran provide this intrinsic as
 only a function, not as a subroutine, or do not support the
 (optional) @var{@2@} argument.
 
-On some systems (specifically SCO) it might be necessary to link the
-``socket'' library if you call this routine, i.e.@: append
-@samp{-lg2c -lsocket -lm} to the @code{g77} arguments.
+On some systems (specifically SCO) it may be necessary to link the
+``socket'' library if you call this routine.
+Typically this means adding @samp{-lg2c -lsocket -lm}
+to the @code{g77} command line when linking the program.
 ")
 
 DEFDOC (FLUSH, "Flush buffered output.", "\
@@ -2162,10 +2164,10 @@ Returns in
 
 DEFDOC (FSEEK, "Position file (low-level).", "\
 Attempts to move Fortran unit @var{@1@} to the specified
-@var{Offset}: absolute offset if @var{@2@}=0; relative to the
-current offset if @var{@2@}=1; relative to the end of the file if
-@var{@2@}=2.
-It branches to label @var{@3@} if @var{@1@} is
+@var{@2@}: absolute offset if @var{@3@}=0; relative to the
+current offset if @var{@3@}=1; relative to the end of the file if
+@var{@3@}=2.
+It branches to label @var{@4@} if @var{@1@} is
 not open or if the call otherwise fails.
 ")