* BUGS, NEWS: Regenerate.

From-SVN: r38424

gcc/f/BUGS

-*Note:* This file is automatically generated from the files
-`bugs0.texi' and `bugs.texi'.  `BUGS' is *not* a source file, although
+_Note:_ This file is automatically generated from the files
+`bugs0.texi' and `bugs.texi'.  `BUGS' is _not_ a source file, although
 it is normally included within source distributions.
 
-   This file lists known bugs in the GCC-2.95 version of the GNU
-Fortran compiler.  Copyright (C) 1995, 1996, 1997, 1998,
-1999 Free Software Foundation,
-Inc.  You may copy, distribute, and modify it freely as long as you
-preserve this copyright notice and permission notice.
+   This file lists known bugs in the GCC-2.97 version of the GNU
+Fortran compiler.  Copyright (C) 1995,1996,1997,1998,1999,2000 Free
+Software Foundation, Inc.  You may copy, distribute, and modify it
+freely as long as you preserve this copyright notice and permission
+notice.
 
 Known Bugs In GNU Fortran
 *************************
 
-   This section identifies bugs that `g77' *users* might run into in
-the GCC-2.95 version of `g77'.  This includes bugs that are actually in
+   This section identifies bugs that `g77' _users_ might run into in
+the GCC-2.97 version of `g77'.  This includes bugs that are actually in
 the `gcc' back end (GBE) or in `libf2c', because those sets of code are
 at least somewhat under the control of (and necessarily intertwined
 with) `g77', so it isn't worth separating them out.
 
-   For information on bugs in *other* versions of `g77', see
-`egcs/gcc/f/NEWS'.  There, lists of bugs fixed in various versions of
+   For information on bugs in _other_ versions of `g77', see
+`gcc/gcc/f/NEWS'.  There, lists of bugs fixed in various versions of
 `g77' can help determine what bugs existed in prior versions.
 
-   *Warning:* The information below is still under development, and
+   _Warning:_ The information below is still under development, and
 might not accurately reflect the `g77' code base of which it is a part.
 Efforts are made to keep it somewhat up-to-date, but they are
 particularly concentrated on any version of this information that is
-distributed as part of a *released* `g77'.
+distributed as part of a _released_ `g77'.
 
    In particular, while this information is intended to apply to the
-GCC-2.95 version of `g77', only an official *release* of that version
+GCC-2.97 version of `g77', only an official _release_ of that version
 is expected to contain documentation that is most consistent with the
 `g77' product in that version.
 
    An online, "live" version of this document (derived directly from
-the mainline, development version of `g77' within `egcs') is available
-via `http://www.gnu.org/software/gcc/onlinedocs/g77_bugs.html'.  Follow the
-"Known Bugs" link.
+the mainline, development version of `g77' within `gcc') is available
+via `http://www.gnu.org/software/gcc/onlinedocs/g77_bugs.html'.  Follow
+the "Known Bugs" link.
 
    For information on bugs that might afflict people who configure,
 port, build, and install `g77', see "Problems Installing" in
-`egcs/gcc/f/INSTALL'.
+`gcc/gcc/f/INSTALL'.
 
-   The following information was last updated on 1999-06-28:
+   The following information was last updated on 2000-11-05:
 
    * `g77' fails to warn about use of a "live" iterative-DO variable as
      an implied-DO variable in a `WRITE' or `PRINT' statement (although
@@ -79,7 +79,7 @@ port, build, and install `g77', see "Problems Installing" in
      assembler file.  This is to be mitigated somewhat in version 0.6.
 
      Version 0.5.18 improves cases like this--specifically, cases of
-     *sparse* initialization that leave large, contiguous areas
+     _sparse_ initialization that leave large, contiguous areas
      uninitialized--significantly.  However, even with the
      improvements, these cases still require too much memory and CPU
      time.
@@ -93,12 +93,10 @@ port, build, and install `g77', see "Problems Installing" in
      Note that `g77' does display a warning message to notify the user
      before the compiler appears to hang.
 
-   * `g77' doesn't emit variable and array members of common blocks for
-     use with a debugger (the `-g' command-line option).  The code is
-     present to do this, but doesn't work with at least one debug
-     format--perhaps it works with others.  And it turns out there's a
-     similar bug for local equivalence areas, so that has been disabled
-     as well.
+   * Previous versions of `g77' didn't emit information on variable and
+     array members of common blocks and equivalences for use with a
+     debugger (the `-g' command-line option).  As of the version of
+     `g77' shipped with version 3.0 of `GCC', this is corrected.
 
      As of Version 0.5.19, a temporary kludge solution is provided
      whereby some rudimentary information on a member is written as a
@@ -152,9 +150,9 @@ port, build, and install `g77', see "Problems Installing" in
 
      While the `g77' and `netlib' versions of `libf2c' differ on how
      this is accomplished, the main differences are that we believe the
-     `g77' version works properly even in the presence of *partially*
+     `g77' version works properly even in the presence of _partially_
      aliased operands.
 
      However, these modifications have reduced performance on targets
      such as x86, due to the extra copies of operands involved.
-
+   

gcc/f/ChangeLog

+Thu Dec 21 20:00:48 2000  Joseph S. Myers  <jsm28@cam.ac.uk>
+
+	* BUGS, NEWS: Regenerate.
+
 2000-12-18  Joseph S. Myers  <jsm28@cam.ac.uk>
 
 	* com.c [VMS]: Remove definition of BSTRING.