990718, very close to release.

testsuite temporarily removed from snapshots because of copyright checks.

9 files changed, 160 insertions, 1324 deletions

diff --git a/gnu/egcs/gcc/f/BUGS b/gnu/egcs/gcc/f/BUGS
index 398b729daad..2efe6e259c2 100644
--- a/gnu/egcs/gcc/f/BUGS
+++ b/gnu/egcs/gcc/f/BUGS
@@ -2,7 +2,7 @@
 `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 FSF-0.5.25 version of the GNU
+   This file lists known bugs in the GCC-2.95 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.
@@ -11,9 +11,9 @@ Known Bugs In GNU Fortran
 *************************
 
    This section identifies bugs that `g77' *users* might run into in
-the FSF-0.5.25 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
+the GCC-2.95 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
@@ -27,7 +27,7 @@ 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
-FSF-0.5.25 version of `g77', only an official *release* of that version
+GCC-2.95 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.
 
@@ -40,15 +40,7 @@ via `http://egcs.cygnus.com/onlinedocs/g77_bugs.html'.  Follow the
 port, build, and install `g77', see "Problems Installing" in
 `egcs/gcc/f/INSTALL'.
 
-   The following information was last updated on 1999-06-25:
-
-   * Input to a `NAMELIST' read involving a repeat count, such as
-     `K(5)=10*3', is not properly handled by `libf2c'.  The first item
-     is written to `K(5)', but the remaining nine are written elsewhere
-     (still within the array), not necessarily starting at `K(6)'.
-
-     A fix is pending, certainly for `gcc' 3.0, perhaps for 2.96 if
-     such a release is made.
+   The following information was last updated on 1999-06-29:
 
    * `g77' fails to warn about use of a "live" iterative-DO variable as
      an implied-DO variable in a `WRITE' or `PRINT' statement (although
diff --git a/gnu/egcs/gcc/f/ChangeLog b/gnu/egcs/gcc/f/ChangeLog
index 2fbcf24d293..d82b2574f07 100644
--- a/gnu/egcs/gcc/f/ChangeLog
+++ b/gnu/egcs/gcc/f/ChangeLog
@@ -1,3 +1,28 @@
+Sat Jul 17 21:57:07 1999  Jeffrey A Law  (law@cygnus.com)
+
+	* root.texi: Clear DEVEOPMENT per Craig's instructions.
+
+1999-07-17  Alexandre Oliva  <oliva@dcc.unicamp.br>
+        
+	* root.texi: Update e-mail addresses to gcc.gnu.org.
+	* g77spec.c (lang_specific_driver): Updated URL with bug reporting 
+	instructions to gcc.gnu.org.  Removed e-mail address.
+
+Sat Jul 17 11:28:43 1999  Craig Burley  <craig@jcb-sc.com>
+
+	* root.texi, g77install.texi: Switchover to GCC terminology.
+	Also, FSF-G77 had been mistakenly set at some point.
+
+Thu Jul  8 15:38:50 1999  Craig Burley  <craig@jcb-sc.com>
+
+	* news.texi: Describe DATE intrinsic fix.
+
+Tue Jun 29 10:10:25 1999  Craig Burley  <craig@jcb-sc.com>
+
+	* bugs.texi: Undo Friday's change, as there's now a fix
+	available from netlib.
+	* news.texi: Document the fix.
+
 Mon Jun 28 10:43:11 1999  Craig Burley  <craig@jcb-sc.com>
 
 	* com.c (ffecom_prepare_expr_): A COMPLEX intrinsic needs
@@ -10,7 +35,7 @@ Fri Jun 25 11:06:32 1999  Craig Burley  <craig@jcb-sc.com>
 	* bugs.texi: Describe K(5)=10*3 NAMELIST-read bug.
 
 Mon Jun 21 12:40:17 1999  Gerald Pfeifer  <pfeifer@dbai.tuwien.ac.at>
- 
+
 	* g77.texi: Update links.
 
 Wed Jun 16 11:43:02 1999  Craig Burley  <craig@jcb-sc.com>
diff --git a/gnu/egcs/gcc/f/INSTALL b/gnu/egcs/gcc/f/INSTALL
index e0349ec0cc8..91858800958 100644
--- a/gnu/egcs/gcc/f/INSTALL
+++ b/gnu/egcs/gcc/f/INSTALL
@@ -13,15 +13,10 @@ Installing GNU Fortran
 
    The following information describes how to install `g77'.
 
-   The information in this file generally pertains to dealing with
-*source* distributions of `g77' and `gcc'.  It is possible that some of
-this information will be applicable to some *binary* distributions of
-these products--however, since these distributions are not made by the
-maintainers of `g77', responsibility for binary distributions rests with
-whoever built and first distributed them.
-
-   Nevertheless, efforts to make `g77' easier to both build and install
-from source and package up as a binary distribution are ongoing.
+   Note that, for users of the GCC-2.95 version of `g77', much of the
+information is obsolete, and is superceded by the GCC installation
+procedures.  Such information is accordingly omitted and flagged as
+such.
 
    *Warning:* The information below is still under development, and
 might not accurately reflect the `g77' code base of which it is a part.
@@ -30,230 +25,17 @@ 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
-FSF-0.5.25 version of `g77', only an official *release* of that version
+GCC-2.95 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.
 
-   The following information was last updated on 1999-05-10:
+   The following information was last updated on 1999-07-17:
 
 Prerequisites
 =============
 
-   The procedures described to unpack, configure, build, and install
-`g77' assume your system has certain programs already installed.
-
-   The following prerequisites should be met by your system before you
-follow the `g77' installation instructions:
-
-`gzip' and `tar'
-     To unpack the `gcc' and `g77' distributions, you'll need the
-     `gunzip' utility in the `gzip' distribution.  Most UNIX systems
-     already have `gzip' installed.  If yours doesn't, you can get it
-     from the FSF.
-
-     Note that you'll need `tar' and other utilities as well, but all
-     UNIX systems have these.  There are GNU versions of all these
-     available--in fact, a complete GNU UNIX system can be put together
-     on most systems, if desired.
-
-     The version of GNU `gzip' used to package this release is
-     1.2.4.  (The version of GNU `tar' used to package this release is
-     1.12.)
-
-`gcc-2.8.1.tar.gz'
-     You need to have this, or some other applicable, version of `gcc'
-     on your system.  The version should be an exact copy of a
-     distribution from the FSF.  Its size is approximately 8.4MB.
-
-     If you've already unpacked `gcc-2.8.1.tar.gz' into a directory
-     (named `gcc-2.8.1') called the "source tree" for `gcc', you can
-     delete the distribution itself, but you'll need to remember to
-     skip any instructions to unpack this distribution.
-
-     Without an applicable `gcc' source tree, you cannot build `g77'.
-     You can obtain an FSF distribution of `gcc' from the FSF.
-
-`g77-0.5.25.tar.gz'
-     You probably have already unpacked this package, or you are
-     reading an advance copy of these installation instructions, which
-     are contained in this distribution.  The size of this package is
-     approximately 1.4MB.
-
-     You can obtain an FSF distribution of `g77' from the FSF, the same
-     way you obtained `gcc'.
-
-Enough disk space
-     The amount of disk space needed to unpack, build, install, and use
-     `g77' depends on the type of system you're using, how you build
-     `g77', and how much of it you install (primarily, which languages
-     you install).
-
-     The sizes shown below assume all languages distributed in
-     `gcc-2.8.1', plus `g77', will be built and installed.  These sizes
-     are indicative of GNU/Linux systems on Intel x86 running COFF and
-     on Digital Alpha (AXP) systems running ELF.  These should be
-     fairly representative of 32-bit and 64-bit systems, respectively.
-
-     Note that all sizes are approximate and subject to change without
-     notice!  They are based on preliminary releases of g77 made shortly
-     before the public beta release.
-
-        -- `gcc' and `g77' distributions occupy 10MB packed, 40MB
-          unpacked.  These consist of the source code and documentation,
-          plus some derived files (mostly documentation), for `gcc' and
-          `g77'.  Any deviations from these numbers for different kinds
-          of systems are likely to be very minor.
-
-        -- A "bootstrap" build requires an additional 91MB for a total
-          of 132MB on an ix86, and an additional 136MB for a total of
-          177MB on an Alpha.
-
-        -- Removing `gcc/stage1' after the build recovers 13MB for a
-          total of 119MB on an ix86, and recovers 21MB for a total of
-          155MB on an Alpha.
-
-          After doing this, the integrity of the build can still be
-          verified via `make compare', and the `gcc' compiler modified
-          and used to build itself for testing fairly quickly, using
-          the copy of the compiler kept in `gcc/stage2'.
-
-        -- Removing `gcc/stage2' after the build further recovers 39MB
-          for a total of 80MB, and recovers 57MB for a total of 98MB on
-          an Alpha.
-
-          After doing this, the compiler can still be installed,
-          especially if GNU `make' is used to avoid gratuitous rebuilds
-          (or, the installation can be done by hand).
-
-        -- Installing `gcc' and `g77' copies 23MB onto the `--prefix'
-          disk for a total of 103MB on an ix86, and copies 31MB onto
-          the `--prefix' disk for a total of 130MB on an Alpha.
-
-     After installation, if no further modifications and builds of
-     `gcc' or `g77' are planned, the source and build directory may be
-     removed, leaving the total impact on a system's disk storage as
-     that of the amount copied during installation.
-
-     Systems with the appropriate version of `gcc' installed don't
-     require the complete bootstrap build.  Doing a "straight build"
-     requires about as much space as does a bootstrap build followed by
-     removing both the `gcc/stage1' and `gcc/stage2' directories.
-
-     Installing `gcc' and `g77' over existing versions might require
-     less *new* disk space, but note that, unlike many products, `gcc'
-     installs itself in a way that avoids overwriting other installed
-     versions of itself, so that other versions may easily be invoked
-     (via `gcc -V VERSION').
-
-     So, the amount of space saved as a result of having an existing
-     version of `gcc' and `g77' already installed is not
-     much--typically only the command drivers (`gcc', `g77', `g++', and
-     so on, which are small) and the documentation is overwritten by
-     the new installation.  The rest of the new installation is done
-     without replacing existing installed versions (assuming they have
-     different version numbers).
-
-`make'
-     Your system must have `make', and you will probably save yourself
-     a lot of trouble if it is GNU `make' (sometimes referred to as
-     `gmake').  In particular, you probably need GNU `make' to build
-     outside the source directory (with `configure''s `--srcdir'
-     option.)
-
-     The version of GNU `make' used to develop this release is
-     3.76.1.
-
-`cc'
-     Your system must have a working C compiler.  If it doesn't, you
-     might be able to obtain a prebuilt binary of some version of `gcc'
-     from the network or on CD-ROM, perhaps from the FSF.  The best
-     source of information about binaries is probably a system-specific
-     Usenet news group, initially via its FAQ.
-
-     *Note Installing GNU CC: (gcc)Installation, for more information
-     on prerequisites for installing `gcc'.
-
-`sed'
-     All UNIX systems have `sed', but some have a broken version that
-     cannot handle configuring, building, or installing `gcc' or `g77'.
-
-     The version of GNU `sed' used to develop this release is
-     2.05.  (Note that GNU `sed' version 3.0 was withdrawn by the
-     FSF--if you happen to have this version installed, replace it with
-     version 2.05 immediately.  See a GNU distribution site for further
-     explanation.)
-
-`root' access or equivalent
-     To perform the complete installation procedures on a system, you
-     need to have `root' access to that system, or equivalent access to
-     the `--prefix' directory tree specified on the `configure' command
-     line.
-
-     Portions of the procedure (such as configuring and building `g77')
-     can be performed by any user with enough disk space and virtual
-     memory.
-
-     However, these instructions are oriented towards less-experienced
-     users who want to install `g77' on their own personal systems.
-
-     System administrators with more experience will want to determine
-     for themselves how they want to modify the procedures described
-     below to suit the needs of their installation.
-
-`autoconf'
-     The version of GNU `autoconf' used to develop this release is
-     2.12.
-
-     `autoconf' is not needed in the typical case of installing `gcc'
-     and `g77'.  *Note Missing tools?::, for information on when it
-     might be needed and how to work around not having it.
-
-`bison'
-     The version of GNU `bison' used to develop this release is
-     1.25.
-
-     `bison' is not needed in the typical case of installing `gcc' and
-     `g77'.  *Note Missing tools?::, for information on when it might
-     be needed and how to work around not having it.
-
-`gperf'
-     The version of GNU `gperf' used to develop this release is
-     2.5.
-
-     `gperf' is not needed in the typical case of installing `gcc' and
-     `g77'.  *Note Missing tools?::, for information on when it might
-     be needed and how to work around not having it.
-
-`makeinfo'
-     The version of GNU `makeinfo' used to develop this release is
-     1.68.
-
-     `makeinfo' is part of the GNU `texinfo' package; `makeinfo'
-     version 1.68 is distributed as part of GNU `texinfo' version
-     3.12.
-
-     `makeinfo' is not needed in the typical case of installing `gcc'
-     and `g77'.  *Note Missing tools?::, for information on when it
-     might be needed and how to work around not having it.
-
-     An up-to-date version of GNU `makeinfo' is still convenient when
-     obtaining a new version of a GNU distribution such as `gcc' or
-     `g77', as it allows you to obtain the `.diff.gz' file instead of
-     the entire `.tar.gz' distribution (assuming you have installed
-     `patch').
-
-`patch'
-     The version of GNU `patch' used to develop this release is
-     2.5.
-
-     Beginning with `g77' version 0.5.23, it is no longer necessary to
-     patch the `gcc' back end to build `g77'.
-
-     An up-to-date version of GNU `patch' is still convenient when
-     obtaining a new version of a GNU distribution such as `gcc' or
-     `g77', as it allows you to obtain the `.diff.gz' file instead of
-     the entire `.tar.gz' distribution (assuming you have installed the
-     tools needed to rebuild derived files, such as `makeinfo').
+   For users of the GCC-2.95 version of `g77', this information is
+superceded by the GCC installation instructions.
 
 Problems Installing
 ===================
@@ -302,46 +84,7 @@ not yet established.
 Missing strtoul or bsearch
 ..........................
 
-   On SunOS4 systems, linking the `f771' program used to produce an
-error message concerning an undefined symbol named `_strtoul', because
-the `strtoul' library function is not provided on that system.
-
-   Other systems have, in the past, been reported to not provide their
-own `strtoul' or `bsearch' function.
-
-   Some versions `g77' tried to default to providing bare-bones
-versions of `bsearch' and `strtoul' automatically, but every attempt at
-this has failed for at least one kind of system.
-
-   To limit the failures to those few systems actually missing the
-required routines, the bare-bones versions are still provided, in
-`egcs/gcc/f/proj.c', if the appropriate macros are defined.  These are
-`NEED_BSEARCH' for `bsearch' and `NEED_STRTOUL' for `NEED_STRTOUL'.
-
-   Therefore, if you are sure your system is missing `bsearch' or
-`strtoul' in its library, define the relevant macro(s) before building
-`g77'.  This can be done by editing `egcs/gcc/f/proj.c' and inserting
-either or both of the following `#define' statements before the comment
-shown:
-
-     /* Insert #define statements here.  */
-     
-     #define NEED_BSEARCH
-     #define NEED_STRTOUL
-
-   Then, continue configuring and building `g77' as usual.
-
-   Or, you can define these on the `make' command line.  To build with
-the bundled `cc' on SunOS4, for example, try:
-     make bootstrap BOOT_CFLAGS='-O2 -g -DNEED_STRTOUL'
-
-   If you then encounter problems compiling `egcs/gcc/f/proj.c', it
-might be due to a discrepancy between how `bsearch' or `strtoul' are
-defined by that file and how they're declared by your system's header
-files.
-
-   In that case, you'll have to use some basic knowledge of C to work
-around the problem, perhaps by editing `egcs/gcc/f/proj.c' somewhat.
+   This information does not apply to the GCC-2.95 version of `g77',
 
 Cleanup Kills Stage Directories
 ...............................
@@ -592,970 +335,18 @@ support 64-bit systems.
 Quick Start
 ===========
 
-   This procedure configures, builds, and installs `g77' "out of the
-box" and works on most UNIX systems.  Each command is identified by a
-unique number, used in the explanatory text that follows.  For the most
-part, the output of each command is not shown, though indications of
-the types of responses are given in a few cases.
-
-   To perform this procedure, the installer must be logged in as user
-`root'.  Much of it can be done while not logged in as `root', and
-users experienced with UNIX administration should be able to modify the
-procedure properly to do so.
-
-   Following traditional UNIX conventions, it is assumed that the
-source trees for `g77' and `gcc' will be placed in `/usr/src'.  It also
-is assumed that the source distributions themselves already reside in
-`/usr/FSF', a naming convention used by the author of `g77' on his own
-system:
-
-     /usr/FSF/gcc-2.8.1.tar.gz
-     /usr/FSF/g77-0.5.25.tar.gz
-
-   If you vary *any* of the steps below, you might run into trouble,
-including possibly breaking existing programs for other users of your
-system.  Before doing so, it is wise to review the explanations of some
-of the steps.  These explanations follow this list of steps.
-
-     sh[ 1]# cd /usr/src
-     
-     sh[ 2]# gunzip -c < /usr/FSF/gcc-2.8.1.tar.gz | tar xf -
-     [Might say "Broken pipe"...that is normal on some systems.]
-     
-     sh[ 3]# gunzip -c < /usr/FSF/g77-0.5.25.tar.gz | tar xf -
-     ["Broken pipe" again possible.]
-     
-     sh[ 4]# ln -s gcc-2.8.1 gcc
-     
-     sh[ 5]# ln -s g77-0.5.25 g77
-     
-     sh[ 6]# mv -i g77/* gcc
-     [No questions should be asked by mv here; or, you made a mistake.]
-     
-     sh[ 7]# cd gcc
-     sh[ 8]# ./configure --prefix=/usr
-     [Do not do the above if gcc is not installed in /usr/bin.
-     You might need a different --prefix=..., as
-     described below.]
-     
-     sh[ 9]# make bootstrap
-     [This takes a long time, and is where most problems occur.]
-     
-     sh[10]# make compare
-     [This verifies that the compiler is `sane'.
-     If any files are printed, you have likely found a g77 bug.]
-     
-     sh[11]# rm -fr stage1
-     
-     sh[12]# make -k install
-     [The actual installation.]
-     
-     sh[13]# g77 -v
-     [Verify that g77 is installed, obtain version info.]
-     
-     sh[14]#
-
-   *Note Updating Your Info Directory: Updating Documentation, for
-information on how to update your system's top-level `info' directory
-to contain a reference to this manual, so that users of `g77' can
-easily find documentation instead of having to ask you for it.
-
-   Elaborations of many of the above steps follows:
-
-Step 1: `cd /usr/src'
-     You can build `g77' pretty much anyplace.  By convention, this
-     manual assumes `/usr/src'.  It might be helpful if other users on
-     your system knew where to look for the source code for the
-     installed version of `g77' and `gcc' in any case.
-
-Step 3: `gunzip -d < /usr/FSF/g77-0.5.25.tar.gz | tar xf -'
-     It is not always necessary to obtain the latest version of `g77'
-     as a complete `.tar.gz' file if you have a complete, earlier
-     distribution of `g77'.  If appropriate, you can unpack that earlier
-     version of `g77', and then apply the appropriate patches to
-     achieve the same result--a source tree containing version
-     0.5.25 of `g77'.
-
-Step 4: `ln -s gcc-2.8.1 gcc'
-
-Step 5: `ln -s g77-0.5.25 g77'
-     These commands mainly help reduce typing, and help reduce visual
-     clutter in examples in this manual showing what to type to install
-     `g77'.
-
-     *Note Unpacking::, for information on using distributions of `g77'
-     made by organizations other than the FSF.
-
-Step 6: `mv -i g77/* gcc'
-     After doing this, you can, if you like, type `rm g77' and `rmdir
-     g77-0.5.25' to remove the empty directory and the symbol link to
-     it.  But, it might be helpful to leave them around as quick
-     reminders of which version(s) of `g77' are installed on your
-     system.
-
-     *Note Unpacking::, for information on the contents of the `g77'
-     directory (as merged into the `gcc' directory).
-
-Step 8: `./configure --prefix=/usr'
-     This is where you specify that the `g77' and `gcc' executables are
-     to be installed in `/usr/bin/', the `g77' and `gcc' documentation
-     is to be installed in `/usr/info/' and `/usr/man/', and so on.
-
-     You should ensure that any existing installation of the `gcc'
-     executable is in `/usr/bin/'.
-
-     However, if that existing version of `gcc' is not 2.8.1, or if you
-     simply wish to avoid risking overwriting it with a newly built
-     copy of the same version, you can specify `--prefix=/usr/local'
-     (which is the default) or some other path, and invoke the newly
-     installed version directly from that path's `bin' directory.
-
-     *Note Where in the World Does Fortran (and GNU CC) Go?: Where to
-     Install, for more information on determining where to install
-     `g77'.  *Note Configuring gcc::, for more information on the
-     configuration process triggered by invoking the `./configure'
-     script.
-
-Step 9: `make bootstrap'
-     *Note Installing GNU CC: (gcc)Installation, for information on the
-     kinds of diagnostics you should expect during this procedure.
-
-     *Note Building gcc::, for complete `g77'-specific information on
-     this step.
-
-Step 10: `make compare'
-     *Note Where to Port Bugs: Bug Lists, for information on where to
-     report that you observed files having different contents during
-     this phase.
-
-     *Note How to Report Bugs: Bug Reporting, for information on *how*
-     to report bugs like this.
-
-Step 11: `rm -fr stage1'
-     You don't need to do this, but it frees up disk space.
-
-Step 12: `make -k install'
-     If this doesn't seem to work, try:
-
-          make -k install install-libf77
-
-     Or, make sure you're using GNU `make'.
-
-     *Note Installation of Binaries::, for more information.
-
-     *Note Updating Your Info Directory: Updating Documentation, for
-     information on entering this manual into your system's list of
-     texinfo manuals.
-
-Step 13: `g77 -v'
-     If this command prints approximately 25 lines of output, including
-     the GNU Fortran Front End version number (which should be the same
-     as the version number for the version of `g77' you just built and
-     installed) and the version numbers for the three parts of the
-     `libf2c' library (`libF77', `libI77', `libU77'), and those version
-     numbers are all in agreement, then there is a high likelihood that
-     the installation has been successfully completed.
-
-     You might consider doing further testing.  For example, log in as
-     a non-privileged user, then create a small Fortran program, such
-     as:
-
-                PROGRAM SMTEST
-                DO 10 I=1, 10
-                   PRINT *, 'Hello World #', I
-          10    CONTINUE
-                END
-
-     Compile, link, and run the above program, and, assuming you named
-     the source file `smtest.f', the session should look like this:
-
-          sh# g77 -o smtest smtest.f
-          sh# ./smtest
-           Hello World # 1
-           Hello World # 2
-           Hello World # 3
-           Hello World # 4
-           Hello World # 5
-           Hello World # 6
-           Hello World # 7
-           Hello World # 8
-           Hello World # 9
-           Hello World # 10
-          sh#
-
-     If invoking `g77' doesn't seem to work, the problem might be that
-     you've installed it in a location that is not in your shell's
-     search path.  For example, if you specified `--prefix=/gnu', and
-     `/gnu/bin' is not in your `PATH' environment variable, you must
-     explicitly specify the location of the compiler via `/gnu/bin/g77
-     -o smtest smtest.f'.
-
-     After proper installation, you don't need to keep your gcc and g77
-     source and build directories around anymore.  Removing them can
-     free up a lot of disk space.
+   For users of the GCC-2.95 version of `g77', this information is
+superceded by the GCC installation instructions.
 
 Complete Installation
 =====================
 
-   Here is the complete `g77'-specific information on how to configure,
-build, and install `g77'.
-
-Unpacking
----------
-
-   The `gcc' source distribution is a stand-alone distribution.  It is
-designed to be unpacked (producing the `gcc' source tree) and built as
-is, assuming certain prerequisites are met (including the availability
-of compatible UNIX programs such as `make', `cc', and so on).
-
-   However, before building `gcc', you will want to unpack and merge
-the `g77' distribution in with it, so that you build a Fortran-capable
-version of `gcc', which includes the `g77' command, the necessary
-run-time libraries, and this manual.
-
-   Unlike `gcc', the `g77' source distribution is *not* a stand-alone
-distribution.  It is designed to be unpacked and, afterwards,
-immediately merged into an applicable `gcc' source tree.  That is, the
-`g77' distribution *augments* a `gcc' distribution--without `gcc',
-generally only the documentation is immediately usable.
-
-   A sequence of commands typically used to unpack `gcc' and `g77' is:
-
-     sh# cd /usr/src
-     sh# gunzip -c /usr/FSF/gcc-2.8.1.tar.gz | tar xf -
-     sh# gunzip -c /usr/FSF/g77-0.5.25.tar.gz | tar xf -
-     sh# ln -s gcc-2.8.1 gcc
-     sh# ln -s g77-0.5.25 g77
-     sh# mv -i g77/* gcc
-
-   *Notes:* The commands beginning with `gunzip...' might print `Broken
-pipe...' as they complete.  That is nothing to worry about, unless you
-actually *hear* a pipe breaking.  The `ln' commands are helpful in
-reducing typing and clutter in installation examples in this manual.
-Hereafter, the top level of `gcc' source tree is referred to as `gcc',
-and the top level of just the `g77' source tree (prior to issuing the
-`mv' command, above) is referred to as `g77'.
-
-   There are three top-level names in a `g77' distribution:
-
-     g77/COPYING.g77
-     g77/README.g77
-     g77/f
-
-   All three entries should be moved (or copied) into a `gcc' source
-tree (typically named after its version number and as it appears in the
-FSF distributions--e.g. `gcc-2.8.1').
-
-   `g77/f' is the subdirectory containing all of the code,
-documentation, and other information that is specific to `g77'.  The
-other two files exist to provide information on `g77' to someone
-encountering a `gcc' source tree with `g77' already present, who has
-not yet read these installation instructions and thus needs help
-understanding that the source tree they are looking at does not come
-from a single FSF distribution.  They also help people encountering an
-unmerged `g77' source tree for the first time.
-
-   *Note:* Please use *only* `gcc' and `g77' source trees as
-distributed by the FSF.  Use of modified versions is likely to result
-in problems that appear to be in the `g77' code but, in fact, are not.
-Do not use such modified versions unless you understand all the
-differences between them and the versions the FSF distributes--in which
-case you should be able to modify the `g77' (or `gcc') source trees
-appropriately so `g77' and `gcc' can coexist as they do in the stock
-FSF distributions.
-
-Merging Distributions
----------------------
-
-   After merging the `g77' source tree into the `gcc' source tree, you
-have put together a complete `g77' source tree.
-
-   As of version 0.5.23, `g77' no longer modifies the version number of
-`gcc', nor does it patch `gcc' itself.
-
-   `g77' still depends on being merged with an appropriate version of
-`gcc'.  For version 0.5.25 of `g77', the specific version of `gcc'
-supported is 2.8.1.
-
-   However, other versions of `gcc' might be suitable "hosts" for this
-version of `g77'.
-
-   GNU version numbers make it easy to figure out whether a particular
-version of a distribution is newer or older than some other version of
-that distribution.  The format is, generally, MAJOR.MINOR.PATCH, with
-each field being a decimal number.  (You can safely ignore leading
-zeros; for example, 1.5.3 is the same as 1.5.03.)  The MAJOR field only
-increases with time.  The other two fields are reset to 0 when the
-field to their left is incremented; otherwise, they, too, only increase
-with time.  So, version 2.6.2 is newer than version 2.5.8, and version
-3.0 is newer than both.  (Trailing `.0' fields often are omitted in
-announcements and in names for distributions and the directories they
-create.)
-
-   If your version of `gcc' is older than the oldest version supported
-by `g77' (as casually determined by listing the contents of
-`egcs/gcc/f/INSTALL/', which contains these installation instructions
-in plain-text format), you should obtain a newer, supported version of
-`gcc'.  (You could instead obtain an older version of `g77', or try and
-get your `g77' to work with the old `gcc', but neither approach is
-recommended, and you shouldn't bother reporting any bugs you find if you
-take either approach, because they're probably already fixed in the
-newer versions you're not using.)
-
-   If your version of `gcc' is newer than the newest version supported
-by `g77', it is possible that your `g77' will work with it anyway.  If
-the version number for `gcc' differs only in the PATCH field, you might
-as well try that version of `gcc'.  Since it has the same MAJOR and
-MINOR fields, the resulting combination is likely to work.
-
-   So, for example, if a particular version of `g77' has support for
-`gcc' versions 2.8.0 and 2.8.1, it is likely that `gcc-2.8.2' would
-work well with `g77'.
-
-   However, `gcc-2.9.0' would almost certainly not work with that
-version of `g77' without appropriate modifications, so a new version of
-`g77' would be needed.
-
-   This complexity is the result of `gcc' and `g77' being separate
-distributions.  By keeping them separate, each product is able to be
-independently improved and distributed to its user base more frequently.
-
-   However, the GBE interface defined by `gcc' typically undergoes some
-incompatible changes at least every time the MINOR field of the version
-number is incremented, and such changes require corresponding changes to
-the `g77' front end (FFE).
-
-Where in the World Does Fortran (and GNU CC) Go?
-------------------------------------------------
-
-   Before configuring, you should make sure you know where you want the
-`g77' and `gcc' binaries to be installed after they're built, because
-this information is given to the configuration tool and used during the
-build itself.
-
-   A `g77' installation normally includes installation of a
-Fortran-aware version of `gcc', so that the `gcc' command recognizes
-Fortran source files and knows how to compile them.
-
-   For this to work, the version of `gcc' that you will be building as
-part of `g77' *must* be installed as the "active" version of `gcc' on
-the system.
-
-   Sometimes people make the mistake of installing `gcc' as
-`/usr/local/bin/gcc', leaving an older, non-Fortran-aware version in
-`/usr/bin/gcc'.  (Or, the opposite happens.)  This can result in `gcc'
-being unable to compile Fortran source files, because when the older
-version of `gcc' is invoked, it complains that it does not recognize
-the language, or the file name suffix.
-
-   So, determine whether `gcc' already is installed on your system,
-and, if so, *where* it is installed, and prepare to configure the new
-version of `gcc' you'll be building so that it installs over the
-existing version of `gcc'.
-
-   You might want to back up your existing copy of `/usr/bin/gcc', and
-the entire `/usr/lib' directory, before you perform the actual
-installation (as described in this manual).
-
-   Existing `gcc' installations typically are found in `/usr' or
-`/usr/local'.  (This means the commands are installed in `/usr/bin' or
-`/usr/local/bin', the libraries in `/usr/lib' or `/usr/local/lib', and
-so on.)
-
-   If you aren't certain where the currently installed version of `gcc'
-and its related programs reside, look at the output of this command:
-
-     gcc -v -o /tmp/delete-me -xc /dev/null -xnone
-
-   All sorts of interesting information on the locations of various
-`gcc'-related programs and data files should be visible in the output
-of the above command.  (The output also is likely to include a
-diagnostic from the linker, since there's no `main_()' function.)
-However, you do have to sift through it yourself; `gcc' currently
-provides no easy way to ask it where it is installed and where it looks
-for the various programs and data files it calls on to do its work.
-
-   Just *building* `g77' should not overwrite any installed
-programs--but, usually, after you build `g77', you will want to install
-it, so backing up anything it might overwrite is a good idea.  (This is
-true for any package, not just `g77', though in this case it is
-intentional that `g77' overwrites `gcc' if it is already installed--it
-is unusual that the installation process for one distribution
-intentionally overwrites a program or file installed by another
-distribution, although, in this case, `g77' is an augmentation of the
-`gcc' distribution.)
-
-   Another reason to back up the existing version first, or make sure
-you can restore it easily, is that it might be an older version on
-which other users have come to depend for certain behaviors.  However,
-even the new version of `gcc' you install will offer users the ability
-to specify an older version of the actual compilation programs if
-desired, and these older versions need not include any `g77' components.
-*Note Specifying Target Machine and Compiler Version: (gcc)Target
-Options, for information on the `-V' option of `gcc'.
-
-Configuring GNU CC
-------------------
-
-   `g77' is configured automatically when you configure `gcc'.  There
-are two parts of `g77' that are configured in two different
-ways--`g77', which "camps on" to the `gcc' configuration mechanism, and
-`libg2c', which uses a variation of the GNU `autoconf' configuration
-system.
-
-   Generally, you shouldn't have to be concerned with either `g77' or
-`libg2c' configuration, unless you're configuring `g77' as a
-cross-compiler.  In this case, the `libg2c' configuration, and possibly
-the `g77' and `gcc' configurations as well, might need special
-attention.  (This also might be the case if you're porting `gcc' to a
-whole new system--even if it is just a new operating system on an
-existing, supported CPU.)
-
-   To configure the system, see *Note Installing GNU CC:
-(gcc)Installation, following the instructions for running `./configure'.
-Pay special attention to the `--prefix=' option, which you almost
-certainly will need to specify.
-
-   (Note that `gcc' installation information is provided as a
-plain-text file in `gcc/INSTALL'.)
-
-   The information printed by the invocation of `./configure' should
-show that the `f' directory (the Fortran language) has been configured.
-If it does not, there is a problem.
-
-   *Note:* Configuring with the `--srcdir' argument, or by starting in
-an empty directory and typing a command such as `../gcc/configure' to
-build with separate build and source directories, is known to work with
-GNU `make', but it is known to not work with other variants of `make'.
-Irix5.2 and SunOS4.1 versions of `make' definitely won't work outside
-the source directory at present.
-
-   `g77''s portion of the `configure' script used to issue a warning
-message about this when configuring for building binaries outside the
-source directory, but no longer does this as of version 0.5.23.
-
-   Instead, `g77' simply rejects most common attempts to build it using
-a non-GNU `make' when the build directory is not the same as the source
-directory, issuing an explanatory diagnostic.
-
-Building GNU CC
----------------
-
-   Building `g77' requires building enough of `gcc' that these
-instructions assume you're going to build all of `gcc', including
-`g++', `protoize', and so on.  You can save a little time and disk
-space by changes the `LANGUAGES' macro definition in `gcc/Makefile.in'
-or `gcc/Makefile', but if you do that, you're on your own.  One change
-is almost *certainly* going to cause failures: removing `c' or `f77'
-from the definition of the `LANGUAGES' macro.
-
-   After configuring `gcc', which configures `g77' and `libg2c'
-automatically, you're ready to start the actual build by invoking
-`make'.
-
-   *Note:* You *must* have run the `configure' script in `gcc' before
-you run `make', even if you're using an already existing `gcc'
-development directory, because `./configure' does the work to recognize
-that you've added `g77' to the configuration.
-
-   There are two general approaches to building GNU CC from scratch:
-
-"bootstrap"
-     This method uses minimal native system facilities to build a
-     barebones, unoptimized `gcc', that is then used to compile
-     ("bootstrap") the entire system.
-
-"straight"
-     This method assumes a more complete native system exists, and uses
-     that just once to build the entire system.
-
-   On all systems without a recent version of `gcc' already installed,
-the bootstrap method must be used.  In particular, `g77' uses
-extensions to the C language offered, apparently, only by `gcc'.
-
-   On most systems with a recent version of `gcc' already installed,
-the straight method can be used.  This is an advantage, because it
-takes less CPU time and disk space for the build.  However, it does
-require that the system have fairly recent versions of many GNU
-programs and other programs, which are not enumerated here.
-
-Bootstrap Build
-...............
-
-   A complete bootstrap build is done by issuing a command beginning
-with `make bootstrap ...', as described in *Note Installing GNU CC:
-(gcc)Installation.  This is the most reliable form of build, but it
-does require the most disk space and CPU time, since the complete system
-is built twice (in Stages 2 and 3), after an initial build (during
-Stage 1) of a minimal `gcc' compiler using the native compiler and
-libraries.
-
-   You might have to, or want to, control the way a bootstrap build is
-done by entering the `make' commands to build each stage one at a time,
-as described in the `gcc' manual.  For example, to save time or disk
-space, you might want to not bother doing the Stage 3 build, in which
-case you are assuming that the `gcc' compiler you have built is
-basically sound (because you are giving up the opportunity to compare a
-large number of object files to ensure they're identical).
-
-   To save some disk space during installation, after Stage 2 is built,
-you can type `rm -fr stage1' to remove the binaries built during Stage
-1.
-
-   Also, see *Note Installing GNU CC: (gcc)Installation, for important
-information on building `gcc' that is not described in this `g77'
-manual.  For example, explanations of diagnostic messages and whether
-they're expected, or indicate trouble, are found there.
-
-Straight Build
-..............
-
-   If you have a recent version of `gcc' already installed on your
-system, and if you're reasonably certain it produces code that is
-object-compatible with the version of `gcc' you want to build as part
-of building `g77', you can save time and disk space by doing a straight
-build.
-
-   To build just the compilers along with the necessary run-time
-libraries, issue the following command:
-
-     make -k CC=gcc
-
-   If you run into problems using this method, you have two options:
-
-   * Abandon this approach and do a bootstrap build.
-
-   * Try to make this approach work by diagnosing the problems you're
-     running into and retrying.
-
-   Especially if you do the latter, you might consider submitting any
-solutions as bug/fix reports.  *Note Known Causes of Trouble with GNU
-Fortran: Trouble.
-
-   However, understand that many problems preventing a straight build
-from working are not `g77' problems, and, in such cases, are not likely
-to be addressed in future versions of `g77'.  Consider treating them as
-`gcc' bugs instead.
-
-Pre-installation Checks
------------------------
-
-   Before installing the system, which includes installing `gcc', you
-might want to do some minimum checking to ensure that some basic things
-work.
-
-   Here are some commands you can try, and output typically printed by
-them when they work:
-
-     sh# cd /usr/src/gcc
-     sh# ./g77 -B./ -v
-     g77 version 0.5.25
-     Driving: ./g77 -B./ -v -c -xf77-version /dev/null -xnone
-     Reading specs from ./specs
-     gcc version 2.8.1
-      cpp -lang-c -v -isystem ./include -undef -D__GNUC__=2 ...
-     GNU CPP version 2.8.1 (Alpha GNU/Linux with ELF)
-     #include "..." search starts here:
-     #include <...> search starts here:
-      include
-      /usr/alpha-linux/include
-      /usr/lib/gcc-lib/alpha-linux/2.8.1/include
-      /usr/include
-     End of search list.
-      ./f771 -fnull-version -quiet -dumpbase g77-version.f -version ...
-     GNU F77 version 2.8.1 (alpha-linux) compiled ...
-     GNU Fortran Front End version 0.5.25
-      as -nocpp -o /tmp/cca14485.o /tmp/cca14485.s
-      ld -m elf64alpha -G 8 -O1 -dynamic-linker /lib/ld-linux.so.2 ...
-      /tmp/cca14485
-     __G77_LIBF77_VERSION__: 0.5.25
-     @(#)LIBF77 VERSION 19970919
-     __G77_LIBI77_VERSION__: 0.5.25
-     @(#) LIBI77 VERSION pjw,dmg-mods 19980405
-     __G77_LIBU77_VERSION__: 0.5.25
-     @(#) LIBU77 VERSION 19970919
-     sh# ./xgcc -B./ -v -o /tmp/delete-me -xc /dev/null -xnone
-     Reading specs from ./specs
-     gcc version 2.8.1
-      ./cpp -lang-c -v -isystem ./include -undef ...
-     GNU CPP version 2.8.1 (Alpha GNU/Linux with ELF)
-     #include "..." search starts here:
-     #include <...> search starts here:
-      include
-      /usr/alpha-linux/include
-      /usr/lib/gcc-lib/alpha-linux/2.8.1/include
-      /usr/include
-     End of search list.
-      ./cc1 /tmp/cca18063.i -quiet -dumpbase null.c -version ...
-     GNU C version 2.8.1 (alpha-linux) compiled ...
-      as -nocpp -o /tmp/cca180631.o /tmp/cca18063.s
-      ld -m elf64alpha -G 8 -O1 -dynamic-linker /lib/ld-linux.so.2 ...
-     /usr/lib/crt1.o: In function `_start':
-     ../sysdeps/alpha/elf/start.S:77: undefined reference to `main'
-     ../sysdeps/alpha/elf/start.S:77: undefined reference to `main'
-     sh#
-
-   (Note that long lines have been truncated, and `...'  used to
-indicate such truncations.)
-
-   The above two commands test whether `g77' and `gcc', respectively,
-are able to compile empty (null) source files, whether invocation of
-the C preprocessor works, whether libraries can be linked, and so on.
-
-   If the output you get from either of the above two commands is
-noticeably different, especially if it is shorter or longer in ways
-that do not look consistent with the above sample output, you probably
-should not install `gcc' and `g77' until you have investigated further.
-
-   For example, you could try compiling actual applications and seeing
-how that works.  (You might want to do that anyway, even if the above
-tests work.)
-
-   To compile using the not-yet-installed versions of `gcc' and `g77',
-use the following commands to invoke them.
-
-   To invoke `g77', type:
-
-     /usr/src/gcc/g77 -B/usr/src/gcc/ ...
-
-   To invoke `gcc', type:
-
-     /usr/src/gcc/xgcc -B/usr/src/gcc/ ...
-
-Installation of Binaries
-------------------------
-
-   After configuring, building, and testing `g77' and `gcc', when you
-are ready to install them on your system, type:
-
-     make -k CC=gcc install
-
-   As described in *Note Installing GNU CC: (gcc)Installation, the
-values for the `CC' and `LANGUAGES' macros should be the same as those
-you supplied for the build itself.
-
-   So, the details of the above command might vary if you used a
-bootstrap build (where you might be able to omit both definitions, or
-might have to supply the same definitions you used when building the
-final stage) or if you deviated from the instructions for a straight
-build.
-
-   If the above command does not install `libg2c.a' as expected, try
-this:
-
-     make -k ... install install-libf77
-
-   We don't know why some non-GNU versions of `make' sometimes require
-this alternate command, but they do.  (Remember to supply the
-appropriate definition for `CC' where you see `...' in the above
-command.)
-
-   Note that using the `-k' option tells `make' to continue after some
-installation problems, like not having `makeinfo' installed on your
-system.  It might not be necessary for your system.
-
-   *Note:* `g77' no longer installs files not directly part of `g77',
-such as `/usr/bin/f77', `/usr/lib/libf2c.a', and `/usr/include/f2c.h',
-or their `/usr/local' equivalents.
-
-   *Note Distributing Binaries::, for information on how to accommodate
-systems with no existing non-`g77' `f77' compiler and systems with
-`f2c' installed.
-
-Updating Your Info Directory
-----------------------------
-
-   As part of installing `g77', you should make sure users of `info'
-can easily access this manual on-line.
-
-   `g77' does this automatically by invoking the `install-info' command
-when you use `make install' to install `g77'.
-
-   If that fails, or if the `info' directory it updates is not the one
-normally accessed by users, consider invoking it yourself.  For example:
-
-     install-info --info-dir=/usr/info /usr/info/g77.info
-
-   The above example assumes the `g77' documentation already is
-installed in `/usr/info' and that `/usr/info/dir' is the file you wish
-to update.  Adjust the command accordingly, if those assumptions are
-wrong.
-
-Missing tools?
---------------
-
-   A build of `gcc' might fail due to one or more tools being called
-upon by `make' (during the build or install process), when those tools
-are not installed on your system.
-
-   This situation can result from any of the following actions
-(performed by you or someone else):
-
-   * Changing the source code or documentation yourself (as a developer
-     or technical writer).
-
-   * Applying a patch that changes the source code or documentation
-     (including, sometimes, the official patches distributed by the
-     FSF).
-
-   * Deleting the files that are created by the (missing) tools.
-
-     The `make maintainer-clean' command is supposed to delete these
-     files, so invoking this command without having all the appropriate
-     tools installed is not recommended.
-
-   * Creating the source directory using a method that does not
-     preserve the date-time-modified information in the original
-     distribution.
-
-     For example, the UNIX `cp -r' command copies a directory tree
-     without preserving the date-time-modified information.  Use `cp
-     -pr' instead.
-
-   The reason these activities cause `make' to try and invoke tools
-that it probably wouldn't when building from a perfectly "clean" source
-directory containing `gcc' and `g77' is that some files in the source
-directory (and the corresponding distribution) aren't really source
-files, but *derived* files that are produced by running tools with the
-corresponding source files as input.  These derived files "depend", in
-`make' terminology, on the corresponding source files.
-
-   `make' determines that a file that depends on another needs to be
-updated if the date-time-modified information for the source file shows
-that it is newer than the corresponding information for the derived
-file.
-
-   If it makes that determination, `make' runs the appropriate commands
-(specified in the "Makefile") to update the derived file, and this
-process typically calls upon one or more installed tools to do the work.
-
-   The "safest" approach to dealing with this situation is to recreate
-the `gcc' and `g77' source directories from complete `gcc' and `g77'
-distributions known to be provided by the FSF.
-
-   Another fairly "safe" approach is to simply install the tools you
-need to complete the build process.  This is especially appropriate if
-you've changed the source code or applied a patch to do so.
-
-   However, if you're certain that the problem is limited entirely to
-incorrect date-time-modified information, that there are no
-discrepancies between the contents of source files and files derived
-from them in the source directory, you can often update the
-date-time-modified information for the derived files to work around the
-problem of not having the appropriate tools installed.
-
-   On UNIX systems, the simplest way to update the date-time-modified
-information of a file is to use the use the `touch' command.
-
-   How to use `touch' to update the derived files updated by each of
-the tools is described below.  *Note:* New versions of `g77' might
-change the set of files it generates by invoking each of these tools.
-If you cannot figure out for yourself how to handle such a situation,
-try an older version of `g77' until you find someone who can (or until
-you obtain and install the relevant tools).
-
-Missing `autoconf'?
-...................
-
-   If you cannot install `autoconf', make sure you have started with a
-*fresh* distribution of `gcc' and `g77', do *not* do `make
-maintainer-clean', and, to ensure that `autoconf' is not invoked by
-`make' during the build, type these commands:
-
-     sh# cd egcs/libf2c
-     sh# touch configure libU77/configure
-     sh# cd ../../..
-     sh#
-
-Missing `bison'?
-................
-
-   If you cannot install `bison', make sure you have started with a
-*fresh* distribution of `gcc', do *not* do `make maintainer-clean',
-and, to ensure that `bison' is not invoked by `make' during the build,
-type these commands:
-
-     sh# cd gcc
-     sh# touch bi-parser.c bi-parser.h c-parse.c c-parse.h cexp.c
-     sh# touch cp/parse.c cp/parse.h objc-parse.c
-     sh# cd ..
-     sh#
-
-Missing `gperf'?
-................
-
-   If you cannot install `gperf', make sure you have started with a
-*fresh* distribution of `gcc', do *not* do `make maintainer-clean',
-and, to ensure that `gperf' is not invoked by `make' during the build,
-type these commands:
-
-     sh# cd gcc
-     sh# touch c-gperf.h
-     sh# cd ..
-     sh#
-
-Missing `makeinfo'?
-...................
-
-   If `makeinfo' is needed but unavailable when installing (via `make
-install'), some files, like `libg2c.a', might not be installed, because
-once `make' determines that it cannot invoke `makeinfo', it cancels any
-further processing.
-
-   If you cannot install `makeinfo', an easy work-around is to specify
-`MAKEINFO=true' on the `make' command line, or to specify the `-k'
-option (`make -k install').
-
-   Another approach is to force the relevant files to be up-to-date by
-typing these commands and then re-trying the installation step:
-
-     sh# cd gcc
-     sh# touch f/g77.info f/BUGS f/INSTALL f/NEWS
-     sh# cd ..
-     sh#
+   For users of the GCC-2.95 version of `g77', this information is
+superceded by the GCC installation instructions.
 
 Distributing Binaries
 =====================
 
-   If you are building `g77' for distribution to others in binary form,
-first make sure you are aware of your legal responsibilities (read the
-file `gcc/COPYING' thoroughly).
-
-   Then, consider your target audience and decide where `g77' should be
-installed.
-
-   For systems like GNU/Linux that have no native Fortran compiler (or
-where `g77' could be considered the native compiler for Fortran and
-`gcc' for C, etc.), you should definitely configure `g77' for
-installation in `/usr/bin' instead of `/usr/local/bin'.  Specify the
-`--prefix=/usr' option when running `./configure'.
-
-   You might also want to set up the distribution so the `f77' command
-is a link to `g77', although a script that accepts "classic" UNIX `f77'
-options and translates the command-line to the appropriate `g77'
-command line would be more appropriate.  If you do this, *please* also
-provide a "man page" in `man/man1/f77.1' describing the command.  (A
-link to `man/man1/g77.1' is appropriate if `bin/f77' is a link to
-`bin/g77'.)
-
-   For a system that might already have `f2c' installed, consider
-whether inter-operation with `g77' will be important to users of `f2c'
-on that system.  If you want to improve the likelihood that users will
-be able to use both `f2c' and `g77' to compile code for a single program
-without encountering link-time or run-time incompatibilities, make sure
-that, whenever they intend to combine `f2c'-produced code with
-`g77'-produced code in an executable, they:
-
-   * Use the `lib/gcc-lib/.../include/g2c.h' file generated by the
-     `g77' build in place of the `f2c.h' file that normally comes with
-     `f2c' (or versions of `g77' prior to 0.5.23) when compiling *all*
-     of the `f2c'-produced C code
-
-   * Link to the `lib/gcc-lib/.../libg2c.a' library built by the `g77'
-     build instead of the `libf2c.a' library that normally comes with
-     `f2c' (or versions of `g77' prior to 0.5.23)
-
-   How you choose to effect the above depends on whether the existing
-installation of `f2c' must be maintained.
-
-   In any case, it is important to try and ensure that the installation
-keeps working properly even after subsequent re-installation of `f2c',
-which probably involves overwriting `/usr/local/lib/libf2c.a' and
-`/usr/local/include/f2c.h', or similar.
-
-   At least, copying `libg2c.a' and `g2c.h' into the appropriate
-"public" directories allows users to more easily select the version of
-`libf2c' they wish to use for a particular build.  The names are
-changed by `g77' to make this coexistence easier to maintain; even if
-`f2c' is installed later, the `g77' files normally installed by its
-installation process aren't disturbed.  Use of symbolic links from one
-set of files to another might result in problems after a subsequent
-reinstallation of either `f2c' or `g77', so be sure to alert users of
-your distribution accordingly.
-
-   (Make sure you clearly document, in the description of your
-distribution, how installation of your distribution will affect
-existing installations of `gcc', `f2c', `f77', `libf2c.a', and so on.
-Similarly, you should clearly document any requirements you assume will
-be met by users of your distribution.)
-
-   For other systems with native `f77' (and `cc') compilers, configure
-`g77' as you (or most of your audience) would configure `gcc' for their
-installations.  Typically this is for installation in `/usr/local', and
-would not include a new version of `/usr/bin/f77' or
-`/usr/local/bin/f77', so users could still use the native `f77'.
-
-   In any case, for `g77' to work properly, you *must* ensure that the
-binaries you distribute include:
-
-`bin/g77'
-     This is the command most users use to compile Fortran.
-
-`bin/gcc'
-     This is the command some users use to compile Fortran, typically
-     when compiling programs written in other languages at the same
-     time.  The `bin/gcc' executable file must have been built from a
-     `gcc' source tree into which a `g77' source tree was merged and
-     configured, or it will not know how to compile Fortran programs.
-
-`info/g77.info*'
-     This is the documentation for `g77'.  If it is not included, users
-     will have trouble understanding diagnostics messages and other
-     such things, and will send you a lot of email asking questions.
-
-     Please edit this documentation (by editing `egcs/gcc/f/*.texi' and
-     doing `make doc' from the `/usr/src/gcc' directory) to reflect any
-     changes you've made to `g77', or at least to encourage users of
-     your binary distribution to report bugs to you first.
-
-     Also, whether you distribute binaries or install `g77' on your own
-     system, it might be helpful for everyone to add a line listing
-     this manual by name and topic to the top-level `info' node in
-     `/usr/info/dir'.  That way, users can find `g77' documentation more
-     easily.  *Note Updating Your Info Directory: Updating
-     Documentation.
-
-`man/man1/g77.1'
-     This is the short man page for `g77'.  It is not always kept
-     up-to-date, but you might as well include it for people who really
-     like "man" pages.
-
-`lib/gcc-lib'
-     This is the directory containing the "private" files installed by
-     and for `gcc', `g77', `g++', and other GNU compilers.
-
-`lib/gcc-lib/.../f771'
-     This is the actual Fortran compiler.
-
-`lib/gcc-lib/.../libg2c.a'
-     This is the run-time library for `g77'-compiled programs.
-
-   Whether you want to include the slightly updated (and possibly
-improved) versions of `cc1', `cc1plus', and whatever other binaries get
-rebuilt with the changes the GNU Fortran distribution makes to the GNU
-back end, is up to you.  These changes are highly unlikely to break any
-compilers, because they involve doing things like adding to the list of
-acceptable compiler options (so, for example, `cc1plus' accepts, and
-ignores, options that only `f771' actually processes).
-
-   Please assure users that unless they have a specific need for their
-existing, older versions of `gcc' command, they are unlikely to
-experience any problems by overwriting it with your version--though
-they could certainly protect themselves by making backup copies first!
-
-   Otherwise, users might try and install your binaries in a "safe"
-place, find they cannot compile Fortran programs with your distribution
-(because, perhaps, they're invoking their old version of the `gcc'
-command, which does not recognize Fortran programs), and assume that
-your binaries (or, more generally, GNU Fortran distributions in
-general) are broken, at least for their system.
-
-   Finally, *please* ask for bug reports to go to you first, at least
-until you're sure your distribution is widely used and has been well
-tested.  This especially goes for those of you making any changes to
-the `g77' sources to port `g77', e.g. to OS/2.  <fortran@gnu.org> has
-received a fair number of bug reports that turned out to be problems
-with other peoples' ports and distributions, about which nothing could
-be done for the user.  Once you are quite certain a bug report does not
-involve your efforts, you can forward it to us.
+   For users of the GCC-2.95 version of `g77', this information is
+superceded by the GCC installation instructions.
 
diff --git a/gnu/egcs/gcc/f/NEWS b/gnu/egcs/gcc/f/NEWS
index d9a91b11df2..3849c2d0217 100644
--- a/gnu/egcs/gcc/f/NEWS
+++ b/gnu/egcs/gcc/f/NEWS
@@ -2,7 +2,7 @@
 `news0.texi' and `news.texi'.  `NEWS' is *not* a source file, although
 it is normally included within source distributions.
 
-   This file lists news about the FSF-0.5.25 version (and some other
+   This file lists news about the GCC-2.95 version (and some other
 versions) 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
@@ -50,7 +50,7 @@ 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
-FSF-0.5.25 version of `g77', only an official *release* of that version
+GCC-2.95 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.
 
@@ -66,7 +66,7 @@ about previous `g77' versions up-to-date.
 the mainline, development version of `g77' within `egcs') is available
 at `http://egcs.cygnus.com/onlinedocs/g77_news.html'.
 
-   The following information was last updated on 1999-06-16:
+   The following information was last updated on 1999-07-08:
 
 In 0.5.25, `GCC' 2.95 (`EGCS' 1.2) versus `EGCS' 1.1.2:
 =======================================================
@@ -90,19 +90,28 @@ In 0.5.25, `GCC' 2.95 (`EGCS' 1.2) versus `EGCS' 1.1.2:
   4. `libg2c' (`libf2c') no longer loses track of the file being worked
      on during a `BACKSPACE' operation.
 
-  5. Automatic arrays now seem to be working on HP-UX systems.
+  5. `libg2c' (`libf2c') fixes a bug whereby input to a `NAMELIST' read
+     involving a repeat count, such as `K(5)=10*3', was not properly
+     handled by `libf2c'.  The first item was written to `K(5)', but
+     the remaining nine were written elsewhere (still within the array),
+     not necessarily starting at `K(6)'.
 
-  6. Fix `g77' so it no longer crashes when compiling I/O statements
+  6. Automatic arrays now seem to be working on HP-UX systems.
+
+  7. The `Date' intrinsic now returns the correct result on big-endian
+     systems.
+
+  8. Fix `g77' so it no longer crashes when compiling I/O statements
      using keywords that define `INTEGER' values, such as `IOSTAT=J',
      where J is other than default `INTEGER' (such as `INTEGER*2').
      Instead, it issues a diagnostic.
 
-  7. Fix `g77' so it properly handles `DATA A/RPT*VAL/', where RPT is
+  9. Fix `g77' so it properly handles `DATA A/RPT*VAL/', where RPT is
      not default `INTEGER', such as `INTEGER*2', instead of producing a
      spurious diagnostic.  Also fix `DATA (A(I),I=1,N)', where `N' is
      not default `INTEGER' to work instead of crashing `g77'.
 
-  8. The `-ax' option is now obeyed when compiling Fortran programs.
+ 10. The `-ax' option is now obeyed when compiling Fortran programs.
      (It is passed to the `f771' driver.)
 
    * The new `-fbounds-check' option causes `g77' to compile run-time
@@ -129,7 +138,7 @@ In 0.5.25, `GCC' 2.95 (`EGCS' 1.2) versus `EGCS' 1.1.2:
      to the implementations of these intrinsics using the `EXTERNAL'
      mechanism (which would avoid the new warnings).
 
-  9. `g77' now warns about a reference to a function when the
+ 11. `g77' now warns about a reference to a function when the
      corresponding *subsequent* function program unit disagrees with
      the reference concerning the type of the function.
 
@@ -140,23 +149,23 @@ In 0.5.25, `GCC' 2.95 (`EGCS' 1.2) versus `EGCS' 1.1.2:
    * The `-malign-double' option now reliably aligns *all*
      double-precision variables and arrays on Intel x86 targets.
 
- 10. Even without the `-malign-double' option, `g77' reliably aligns
+ 12. Even without the `-malign-double' option, `g77' reliably aligns
      local double-precision variables that are not in `EQUIVALENCE'
      areas and not `SAVE''d.
 
- 11. `g77' now open-codes ("inlines") division of `COMPLEX' operands
+ 13. `g77' now open-codes ("inlines") division of `COMPLEX' operands
      instead of generating a run-time call to the `libf2c' routines
      `c_div' or `z_div', unless the `-Os' option is specified.
 
    * `g77' no longer generates code to maintain `errno', a C-language
      concept, when performing operations such as the `SqRt' intrinsic.
 
- 12. `g77' developers can temporarily use the `-fflatten-arrays' option
+ 14. `g77' developers can temporarily use the `-fflatten-arrays' option
      to compare how the compiler handles code generation using C-like
      constructs as compared to the Fortran-like method constructs
      normally used.
 
- 13. A substantial portion of the `g77' front end's code-generation
+ 15. A substantial portion of the `g77' front end's code-generation
      component was rewritten.  It now generates code using facilities
      more robustly supported by the `gcc' back end.  One effect of this
      rewrite is that some codes no longer produce a spurious "label LAB
@@ -164,11 +173,11 @@ In 0.5.25, `GCC' 2.95 (`EGCS' 1.2) versus `EGCS' 1.1.2:
 
    * Support for the `-fugly' option has been removed.
 
- 14. Improve documentation and indexing, including information on Year
+ 16. Improve documentation and indexing, including information on Year
      2000 (Y2K) compliance, and providing more information on internals
      of the front end.
 
- 15. Upgrade to `libf2c' as of 1999-05-10.
+ 17. Upgrade to `libf2c' as of 1999-05-10.
 
 In 0.5.24 versus 0.5.23:
 ========================
@@ -231,25 +240,25 @@ In `EGCS' 1.1.1 versus `EGCS' 1.1:
 In `EGCS' 1.1 versus `EGCS' 1.0.3:
 ==================================
 
- 16. Fix bugs in the `libU77' intrinsic `HostNm' that wrote one byte
+ 18. Fix bugs in the `libU77' intrinsic `HostNm' that wrote one byte
      beyond the end of its `CHARACTER' argument, and in the `libU77'
      intrinsics `GMTime' and `LTime' that overwrote their arguments.
 
- 17. Assumed arrays with negative bounds (such as `REAL A(-1:*)') no
+ 19. Assumed arrays with negative bounds (such as `REAL A(-1:*)') no
      longer elicit spurious diagnostics from `g77', even on systems
      with pointers having different sizes than integers.
 
      This bug is not known to have existed in any recent version of
      `gcc'.  It was introduced in an early release of `egcs'.
 
- 18. Valid combinations of `EXTERNAL', passing that external as a dummy
+ 20. Valid combinations of `EXTERNAL', passing that external as a dummy
      argument without explicitly giving it a type, and, in a subsequent
      program unit, referencing that external as an external function
      with a different type no longer crash `g77'.
 
- 19. `CASE DEFAULT' no longer crashes `g77'.
+ 21. `CASE DEFAULT' no longer crashes `g77'.
 
- 20. The `-Wunused' option no longer issues a spurious warning about
+ 22. The `-Wunused' option no longer issues a spurious warning about
      the "master" procedure generated by `g77' for procedures
      containing `ENTRY' statements.
 
@@ -274,25 +283,25 @@ In `EGCS' 1.1 versus `EGCS' 1.0.3:
      `libf2c' environment, even when `libf2c' (now `libg2c') is a
      shared library.
 
- 21. `g77' no longer installs the `f77' command and `f77.1' man page in
+ 23. `g77' no longer installs the `f77' command and `f77.1' man page in
      the `/usr' or `/usr/local' heirarchy, even if the `f77-install-ok'
      file exists in the source or build directory.  See the
      installation documentation for more information.
 
- 22. `g77' no longer installs the `libf2c.a' library and `f2c.h'
+ 24. `g77' no longer installs the `libf2c.a' library and `f2c.h'
      include file in the `/usr' or `/usr/local' heirarchy, even if the
      `f2c-install-ok' or `f2c-exists-ok' files exist in the source or
      build directory.  See the installation documentation for more
      information.
 
- 23. The `libf2c.a' library produced by `g77' has been renamed to
+ 25. The `libf2c.a' library produced by `g77' has been renamed to
      `libg2c.a'.  It is installed only in the `gcc' "private" directory
      heirarchy, `gcc-lib'.  This allows system administrators and users
      to choose which version of the `libf2c' library from `netlib' they
      wish to use on a case-by-case basis.  See the installation
      documentation for more information.
 
- 24. The `f2c.h' include (header) file produced by `g77' has been
+ 26. The `f2c.h' include (header) file produced by `g77' has been
      renamed to `g2c.h'.  It is installed only in the `gcc' "private"
      directory heirarchy, `gcc-lib'.  This allows system administrators
      and users to choose which version of the include file from
@@ -304,11 +313,11 @@ In `EGCS' 1.1 versus `EGCS' 1.0.3:
      than the one built and installed as part of the same `g77' version
      is picked up.
 
- 25. During the configuration and build process, `g77' creates
+ 27. During the configuration and build process, `g77' creates
      subdirectories it needs only as it needs them.  Other cleaning up
      of the configuration and build process has been performed as well.
 
- 26. `install-info' now used to update the directory of Info
+ 28. `install-info' now used to update the directory of Info
      documentation to contain an entry for `g77' (during installation).
 
    * Some diagnostics have been changed from warnings to errors, to
@@ -317,38 +326,38 @@ In `EGCS' 1.1 versus `EGCS' 1.0.3:
      in the `OPEN', `INQUIRE', `READ', and `WRITE' statements, and
      about truncations of various sorts of constants.
 
- 27. Improve compilation of `FORMAT' expressions so that a null byte is
+ 29. Improve compilation of `FORMAT' expressions so that a null byte is
      appended to the last operand if it is a constant.  This provides a
      cleaner run-time diagnostic as provided by `libf2c' for statements
      like `PRINT '(I1', 42'.
 
- 28. Improve documentation and indexing.
+ 30. Improve documentation and indexing.
 
- 29. The upgrade to `libf2c' as of 1998-06-18 should fix a variety of
+ 31. The upgrade to `libf2c' as of 1998-06-18 should fix a variety of
      problems, including those involving some uses of the `T' format
      specifier, and perhaps some build (porting) problems as well.
 
 In `EGCS' 1.1 versus `g77' 0.5.23:
 ==================================
 
- 30. Fix a code-generation bug that afflicted Intel x86 targets when
+ 32. Fix a code-generation bug that afflicted Intel x86 targets when
      `-O2' was specified compiling, for example, an old version of the
      `DNRM2' routine.
 
      The x87 coprocessor stack was being mismanaged in cases involving
      assigned `GOTO' and `ASSIGN'.
 
- 31. `g77' no longer produces incorrect code and initial values for
+ 33. `g77' no longer produces incorrect code and initial values for
      `EQUIVALENCE' and `COMMON' aggregates that, due to "unnatural"
      ordering of members vis-a-vis their types, require initial padding.
 
- 32. Fix `g77' crash compiling code containing the construct
+ 34. Fix `g77' crash compiling code containing the construct
      `CMPLX(0.)' or similar.
 
- 33. `g77' no longer crashes when compiling code containing
+ 35. `g77' no longer crashes when compiling code containing
      specification statements such as `INTEGER(KIND=7) PTR'.
 
- 34. `g77' no longer crashes when compiling code such as `J = SIGNAL(1,
+ 36. `g77' no longer crashes when compiling code such as `J = SIGNAL(1,
      2)'.
 
    * `g77' now treats `%LOC(EXPR)' and `LOC(EXPR)' as "ordinary"
@@ -359,7 +368,7 @@ In `EGCS' 1.1 versus `g77' 0.5.23:
      Previously, `g77' treated these expressions as denoting special
      "pointer" arguments for the purposes of filewide analysis.
 
- 35. Fix `g77' crash (or apparently infinite run-time) when compiling
+ 37. Fix `g77' crash (or apparently infinite run-time) when compiling
      certain complicated expressions involving `COMPLEX' arithmetic
      (especially multiplication).
 
@@ -389,9 +398,9 @@ In `EGCS' 1.1 versus `g77' 0.5.23:
    * The F90 `System_Clock' intrinsic allows the optional arguments
      (except for the `Count' argument) to be omitted.
 
- 36. Upgrade to `libf2c' as of 1998-06-18.
+ 38. Upgrade to `libf2c' as of 1998-06-18.
 
- 37. Improve documentation and indexing.
+ 39. Improve documentation and indexing.
 
 In previous versions:
 =====================
diff --git a/gnu/egcs/gcc/f/bugs.texi b/gnu/egcs/gcc/f/bugs.texi
index a08a0a17155..77665daa6ea 100644
--- a/gnu/egcs/gcc/f/bugs.texi
+++ b/gnu/egcs/gcc/f/bugs.texi
@@ -9,7 +9,7 @@
 @c in the standalone derivations of this file (e.g. BUGS).
 @set copyrights-bugs 1995-1999
 
-@set last-update-bugs 1999-06-25
+@set last-update-bugs 1999-06-29
 
 @include root.texi
 
@@ -98,17 +98,6 @@ The following information was last updated on @value{last-update-bugs}:
 
 @itemize @bullet
 @item
-Input to a @code{NAMELIST} read involving a repeat count,
-such as @samp{K(5)=10*3},
-is not properly handled by @code{libf2c}.
-The first item is written to @samp{K(5)},
-but the remaining nine are written elsewhere (still within the array),
-not necessarily starting at @samp{K(6)}.
-
-A fix is pending, certainly for @code{gcc} 3.0,
-perhaps for 2.96 if such a release is made.
-
-@item
 @code{g77} fails to warn about
 use of a ``live'' iterative-DO variable
 as an implied-DO variable
diff --git a/gnu/egcs/gcc/f/g77install.texi b/gnu/egcs/gcc/f/g77install.texi
index 440829736c8..abc63963554 100644
--- a/gnu/egcs/gcc/f/g77install.texi
+++ b/gnu/egcs/gcc/f/g77install.texi
@@ -9,7 +9,7 @@
 @c in the standalone derivations of this file (e.g. INSTALL).
 @set copyrights 1995-1999
 
-@set last-update-install 1999-05-10
+@set last-update-install 1999-07-17
 
 @include root.texi
 
@@ -30,7 +30,6 @@ this copyright notice and permission notice.
 @chapter Installing GNU Fortran
 @end ifset
 
-@set version-gcc 2.8.1
 @set version-autoconf 2.12
 @set version-bison 1.25
 @set version-gperf 2.5
@@ -50,21 +49,22 @@ this copyright notice and permission notice.
 
 The following information describes how to install @code{g77}.
 
+@clear OMIT-FSF-G77
+
 @ifset EGCS-G77
 @set OMIT-FSF-G77
-Note that, for @code{egcs} users,
+@end ifset
+
+@ifset GCC-G77
+@set OMIT-FSF-G77
+@end ifset
+
+@ifset OMIT-FSF-G77
+Note that, for users of the @value{which-g77} version of @code{g77},
 much of the information is obsolete,
 and is superceded by the
-@code{egcs} installation procedures.
+@value{which-gcc} installation procedures.
 Such information is accordingly omitted and flagged as such.
-@ifset DEVELOPMENT
-@ifclear DOC-INSTALL
-@clear OMIT-FSF-G77
-(It is not actually omitted from the development version of this documentation,
-so the @code{g77} developers can easily find all the documentation
-for all versions of @code{g77} in one place.)
-@end ifclear
-@end ifset
 @end ifset
 
 @ifclear OMIT-FSF-G77
@@ -112,9 +112,10 @@ The following information was last updated on @value{last-update-install}:
 @section Prerequisites
 @cindex prerequisites
 
-@ifset EGCS-G77
-For @code{egcs} users, this information is
-superceded by the @code{egcs} installation instructions.
+@ifset OMIT-FSF-G77
+For users of the @value{which-g77} version of @code{g77},
+this information is superceded by the
+@value{which-gcc} installation instructions.
 @end ifset
 
 @ifclear OMIT-FSF-G77
@@ -482,9 +483,9 @@ is not yet established.
 @cindex @code{ld}, can't find _strtoul
 @cindex SunOS4
 
-@ifset EGCS-G77
-This information does not apply to the
-@code{egcs} version of @code{g77}.
+@ifset OMIT-FSF-G77
+This information does not apply to
+the @value{which-g77} version of @code{g77},
 @end ifset
 
 @ifclear OMIT-FSF-G77
@@ -890,9 +891,10 @@ systems.
 @section Quick Start
 @cindex quick start
 
-@ifset EGCS-G77
-For @code{egcs} users, this information is
-superceded by the @code{egcs} installation instructions.
+@ifset OMIT-FSF-G77
+For users of the @value{which-g77} version of @code{g77},
+this information is superceded by the
+@value{which-gcc} installation instructions.
 @end ifset
 
 @ifclear OMIT-FSF-G77
@@ -1178,9 +1180,10 @@ Removing them can free up a lot of disk space.
 @node Complete Installation
 @section Complete Installation
 
-@ifset EGCS-G77
-For @code{egcs} users, this information is
-superceded by the @code{egcs} installation instructions.
+@ifset OMIT-FSF-G77
+For users of the @value{which-g77} version of @code{g77},
+this information is superceded by the
+@value{which-gcc} installation instructions.
 @end ifset
 
 @ifclear OMIT-FSF-G77
@@ -2048,9 +2051,10 @@ sh#
 @cindex binaries, distributing
 @cindex code, distributing
 
-@ifset EGCS-G77
-For @code{egcs} users, this information is
-superceded by the @code{egcs} installation instructions.
+@ifset OMIT-FSF-G77
+For users of the @value{which-g77} version of @code{g77},
+this information is superceded by the
+@value{which-gcc} installation instructions.
 @end ifset
 
 @ifclear OMIT-FSF-G77
diff --git a/gnu/egcs/gcc/f/news.texi b/gnu/egcs/gcc/f/news.texi
index 9f20e65bf43..9a929c237ec 100644
--- a/gnu/egcs/gcc/f/news.texi
+++ b/gnu/egcs/gcc/f/news.texi
@@ -9,7 +9,7 @@
 @c in the standalone derivations of this file (e.g. NEWS).
 @set copyrights-news 1995-1999
 
-@set last-update-news 1999-06-16
+@set last-update-news 1999-07-08
 
 @include root.texi
 
@@ -193,12 +193,29 @@ during a @code{BACKSPACE} operation.
 
 @ifclear USERVISONLY
 @item
+@code{libg2c} (@code{libf2c}) fixes a bug whereby
+input to a @code{NAMELIST} read involving a repeat count,
+such as @samp{K(5)=10*3},
+was not properly handled by @code{libf2c}.
+The first item was written to @samp{K(5)},
+but the remaining nine were written elsewhere (still within the array),
+not necessarily starting at @samp{K(6)}.
+@end ifclear
+
+@ifclear USERVISONLY
+@item
 @c Tim Prince reported this, regarding the TEST_FPU benchmark.
 Automatic arrays now seem to be working on HP-UX systems.
 @end ifclear
 
 @ifclear USERVISONLY
 @item
+The @code{Date} intrinsic now returns the correct result
+on big-endian systems.
+@end ifclear
+
+@ifclear USERVISONLY
+@item
 Fix @code{g77} so it no longer crashes when compiling
 I/O statements using keywords that define @code{INTEGER} values,
 such as @samp{IOSTAT=@var{j}},
diff --git a/gnu/egcs/gcc/f/root.texi b/gnu/egcs/gcc/f/root.texi
index 37d8286013e..3fb29ee3483 100644
--- a/gnu/egcs/gcc/f/root.texi
+++ b/gnu/egcs/gcc/f/root.texi
@@ -2,29 +2,38 @@
 @c as compared to a release version.  When making a release
 @c (e.g. a release branch in the CVS repository for egcs),
 @c clear this and set the version information correctly.
-@set DEVELOPMENT
+@clear DEVELOPMENT
 @set version-g77 0.5.25
 @set version-egcs 1.2
+@set version-gcc 2.95
 
-@c EGCS-G77 is set to indicate this is the EGCS version of g77.
+@c GCC-G77 indicates this is the GCC (2.95 or later) version of g77.
+@set GCC-G77
+
+@c EGCS-G77 indicates this is the EGCS (1.0 or 1.1) version of g77.
 @clear EGCS-G77
 
-@ifclear EGCS-G77
-@c FSF-G77 is set to indicate this is the FSF version of g77.
-@set FSF-G77
-@end ifclear
+@c FSF-G77 indicates this is the FSF (0.5.23 or earlier) version of g77.
+@clear FSF-G77
 
-@set email-general egcs@@egcs.cygnus.com
-@set email-bugs egcs-bugs@@egcs.cygnus.com
+@set email-general gcc@@gcc.gnu.org
+@set email-bugs gcc-bugs@@gcc.gnu.org
 @set path-g77 egcs/gcc/f
 @set path-libf2c egcs/libf2c
 
+@ifset GCC-G77
+@set which-g77 GCC-@value{version-gcc}
+@set which-gcc GCC
+@end ifset
+
 @ifset EGCS-G77
 @set which-g77 EGCS-@value{version-egcs}
+@set which-gcc EGCS
 @end ifset
 
 @ifset FSF-G77
 @set which-g77 FSF-@value{version-g77}
+@set which-gcc GCC
 @end ifset
 
 @set email-burley craig@@jcb-sc.com
diff --git a/gnu/egcs/gcc/f/version.c b/gnu/egcs/gcc/f/version.c
index cba4229e05d..21369a22dee 100644
--- a/gnu/egcs/gcc/f/version.c
+++ b/gnu/egcs/gcc/f/version.c
@@ -1 +1 @@
-const char *ffe_version_string = "0.5.25 19990628 (prerelease)";
+const char *ffe_version_string = "0.5.25 19990718 (prerelease)";