Update BUGS, INSTALL, NEWS derived files

From-SVN: r25744

gcc/f/BUGS

-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.
+*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 GNU Fortran compiler.  Copyright
-(C) 1995-1998 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 EGCS-1.2 version of the GNU
+Fortran compiler.  Copyright (C) 1995-1999 Free Software Foundation,
+Inc.  You may copy, distribute, and modify it freely as long as you
+preserve this copyright notice and permission notice.
 
-Bugs in GNU Fortran
-*******************
+Known Bugs In GNU Fortran
+*************************
 
    This section identifies bugs that `g77' *users* might run into in
-version {No Value For "version-g77"} 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', *Note News
-About GNU Fortran: News.
+the EGCS-1.2 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
+`g77', can help determine what bugs existed in prior versions.
+
+   *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'.
+
+   In particular, while this information is intended to apply to the
+EGCS-1.2 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://egcs.cygnus.com/onlinedocs/g77_bugs.html'.  Follow the
+"Known Bugs" link.
 
    For information on bugs that might afflict people who configure,
-port, build, and install `g77', *Note Problems Installing::.
+port, build, and install `g77', see "Problems Installing" in
+`egcs/gcc/f/INSTALL'.
+
+   The following information was last updated on 1999-03-13:
 
    * Automatic arrays possibly aren't working on HP-UX systems, at
      least in HP-UX version 10.20.  Writing into them apparently causes
@@ -78,10 +97,7 @@ port, build, and install `g77', *Note Problems Installing::.
      compiler.)
 
      Note that `g77' does display a warning message to notify the user
-     before the compiler appears to hang.  *Note Initialization of
-     Large Aggregate Areas: Large Initialization, for information on
-     how to change the point at which `g77' decides to issue this
-     warning.
+     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
@@ -94,9 +110,6 @@ port, build, and install `g77', *Note Problems Installing::.
      whereby some rudimentary information on a member is written as a
      string that is the member's value as a character string.
 
-     *Note Options for Code Generation Conventions: Code Gen Options,
-     for information on the `-fdebug-kludge' option.
-
    * When debugging, after starting up the debugger but before being
      able to see the source code for the main program unit, the user
      must currently set a breakpoint at `MAIN__' (or `MAIN___' or