release branch changes from 11-27 snapshot to egcs-1.0.

From-SVN: r16970

5 files changed, 28 insertions, 15 deletions

diff --git a/gcc/f/INSTALL b/gcc/f/INSTALL
index cccbe95..5072a55 100644
--- a/gcc/f/INSTALL
+++ b/gcc/f/INSTALL
@@ -3,6 +3,9 @@ compiler.  Copyright (C) 1995, 1996 Free Software Foundation, Inc.  You
 may copy, distribute, and modify it freely as long as you preserve this
 copyright notice and permission notice.
 
+Note most of this information is out of date and superceded by the EGCS
+install procedures.  It is provided for historical reference only.
+
 Installing GNU Fortran
 **********************
 
@@ -1594,7 +1597,7 @@ general) are broken, at least for their system.
 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.ai.mit.edu> has received a fair number of bug reports that
+<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
diff --git a/gcc/f/g77.texi b/gcc/f/g77.texi
index c5b5bb6..d2f3d99 100644
--- a/gcc/f/g77.texi
+++ b/gcc/f/g77.texi
@@ -91,7 +91,7 @@ translations approved by the Free Software Foundation instead of in the
 original English.
 @end ifinfo
 
-Contributed by James Craig Burley (@email{burley@@gnu.ai.mit.edu}).
+Contributed by James Craig Burley (@email{burley@@gnu.org}).
 Inspired by a first pass at translating @file{g77-0.5.16/f/DOC} that
 was contributed to Craig by David Ronis (@email{ronis@@onsager.chem.mcgill.ca}).
 
@@ -762,7 +762,7 @@ without royalty; alteration is not permitted.
 @cindex improvements, funding
 
 Work on GNU Fortran is still being done mostly by its author,
-James Craig Burley (@email{burley@@gnu.ai.mit.edu}), who is a volunteer
+James Craig Burley (@email{burley@@gnu.org}), who is a volunteer
 for, not an employee of, the Free Software Foundation (FSF).
 As with other GNU software, funding is important because it can pay for
 needed equipment, personnel, and so on.
@@ -772,7 +772,7 @@ needed equipment, personnel, and so on.
 The FSF provides information on the best way to fund ongoing
 development of GNU software (such as GNU Fortran) in documents
 such as the ``GNUS Bulletin''.
-Email @email{gnu@@prep.ai.mit.edu} for information on funding the FSF.
+Email @email{gnu@@gnu.org} for information on funding the FSF.
 
 To fund specific GNU Fortran work in particular, the FSF might
 provide a means for that, but the FSF does not provide direct funding
@@ -801,7 +801,7 @@ would be able to plan on not doing contract work for many months and
 could thus devote that time to work on projects (such as the planned
 changes for 0.6) that require longer timeframes to complete.
 For the latest information on the status of the author, do
-@kbd{finger -l burley@@gate.gnu.ai.mit.edu} on a UNIX system
+@kbd{finger -l burley@@gnu.org} on a UNIX system
 (or any system with a command like UNIX @code{finger}).
 
 Another important way to support work on GNU Fortran is to volunteer
@@ -810,7 +810,7 @@ Work is needed on documentation, testing, porting
 to various machines, and in some cases, coding (although major
 changes planned for version 0.6 make it difficult to add manpower to this
 area).
-Email @email{fortran@@gnu.ai.mit.edu} to volunteer for this work.
+Email @email{egcs@@cygnus.com} to volunteer for this work.
 
 @xref{Funding,,Funding Free Software}, for more information.
 
@@ -3251,9 +3251,9 @@ users use @code{g77}.
 such changes to @code{g77}.
 
 To find out about existing bugs and ongoing plans for GNU
-Fortran, retrieve @code{ftp://alpha.gnu.ai.mit.edu/g77.plan}
+Fortran, retrieve @code{ftp://alpha.gnu.org/g77.plan}
 or, if you cannot do that, email
-@email{fortran@@gnu.ai.mit.edu} asking for a recent copy of the
+@email{fortran@@gnu.org} asking for a recent copy of the
 GNU Fortran @file{.plan} file.
 
 @heading In 0.5.21:
@@ -10164,7 +10164,7 @@ or installing @code{g77} is not provided here.
 
 To find out about major bugs discovered in the current release and
 possible workarounds for them, retrieve
-@code{ftp://alpha.gnu.ai.mit.edu/g77.plan}.
+@code{ftp://alpha.gnu.org/g77.plan}.
 
 (Note that some of this portion of the manual is lifted
 directly from the @code{gcc} manual, with minor modifications
@@ -12290,8 +12290,8 @@ exposes it more readily than other compilers.
 @node Bug Lists
 @section Where to Report Bugs
 @cindex bug report mailing lists
-@kindex fortran@@gnu.ai.mit.edu
-Send bug reports for GNU Fortran to @email{fortran@@gnu.ai.mit.edu}.
+@kindex egcs-bugs@@cygnus.com
+Send bug reports for GNU Fortran to @email{egcs-bugs@@cygnus.com}.
 
 Often people think of posting bug reports to a newsgroup instead of
 mailing them.
@@ -12627,7 +12627,7 @@ we should be able to reproduce the crash ourselves.
 If you would like to write bug fixes or improvements for the GNU Fortran
 compiler, that is very helpful.
 Send suggested fixes to the bug report
-mailing list, @email{fortran@@gnu.ai.mit.edu}.
+mailing list, @email{egcs-bugs@@cygnus.com}.
 
 Please follow these guidelines so we can study your patches efficiently.
 If you don't follow these guidelines, your information might still be
@@ -12752,7 +12752,7 @@ The service directory is found in the file named @file{SERVICE} in the
 GNU CC distribution.
 
 @item
-Send a message to @email{fortran@@gnu.ai.mit.edu}.
+Send a message to @email{egcs@@cygnus.com}.
 @end itemize
 
 @end ifset
diff --git a/gcc/f/g77install.texi b/gcc/f/g77install.texi
index acee44a..32bb91e 100644
--- a/gcc/f/g77install.texi
+++ b/gcc/f/g77install.texi
@@ -7,6 +7,9 @@
 
 @c 1997-09-09
 
+Note most of this information is out of date and superceded by the EGCS
+install procedures.  It is provided for historical reference only.
+
 @ifclear INSTALLONLY
 @node Installation
 @chapter Installing GNU Fortran
@@ -2106,7 +2109,7 @@ 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 @code{g77} sources to port @code{g77}, e.g. to OS/2.
-@email{fortran@@gnu.ai.mit.edu} has received a fair number of bug
+@email{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.
diff --git a/gcc/f/gbe/README b/gcc/f/gbe/README
index c30f5d7..f8b7180 100644
--- a/gcc/f/gbe/README
+++ b/gcc/f/gbe/README
@@ -1,3 +1,10 @@
+971202
+It is not necessary to apply the "backend" patch to an egcs based gcc
+release.  The files in this directory are included in the egcs distribution
+for historical purposes only.
+
+
+
 970909
 
 This directory contains .diff files for various GNU CC distributions
diff --git a/gcc/f/lex.c b/gcc/f/lex.c
index acb4391..dbf79dd 100644
--- a/gcc/f/lex.c
+++ b/gcc/f/lex.c
@@ -230,7 +230,7 @@ ffelex_append_to_token_ (char c)
     }
 #ifdef MAP_CHARACTER
 Sorry, MAP_CHARACTER is not going to work as expected in GNU Fortran,
-please contact fortran@gnu.ai.mit.edu if you wish to fund work to
+please contact fortran@gnu.org if you wish to fund work to
 port g77 to non-ASCII machines.
 #endif
   ffelex_token_->text[ffelex_token_->length++] = c;