README.g77, [...]: Update email addresses.

        * README.g77, gcc.c, gcc.texi: Update email addresses.
        * invoke.texi system.h: Likewise.

From-SVN: r25064

6 files changed, 21 insertions, 16 deletions

diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index 30ff75e..0ddb92f 100644
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,8 @@
+Sat Feb  6 18:14:46 1999  Jeffrey A Law  (law@cygnus.com)
+
+	* README.g77, gcc.c, gcc.texi: Update email addresses.
+	* invoke.texi system.h: Likewise.
+
 Sat Feb  6 11:04:08 1999  Jim Wilson  <wilson@cygnus.com>
 
 	* unroll.c (find_splittable_givs): After express_from, call replace_rtx
diff --git a/gcc/README.g77 b/gcc/README.g77
index f22f179..d0f5a4b 100644
--- a/gcc/README.g77
+++ b/gcc/README.g77
@@ -18,7 +18,7 @@ g77, while `[egcs]' denotes egcs-only information.
 
 
 The email address to which bugs are to be reported is either
-[FSF] <fortran@gnu.org> or [egcs] <egcs-bugs@cygnus.com>.
+[FSF] <fortran@gnu.org> or [egcs] <egcs-bugs@egcs.cygnus.com>.
 
 * *DO NOT* send any email (reporting bugs, asking questions, etc.) to
   either of these addresses without *first* reading the g77 documentation.
diff --git a/gcc/gcc.c b/gcc/gcc.c
index 75d2f7e..18faad0 100644
--- a/gcc/gcc.c
+++ b/gcc/gcc.c
@@ -4942,7 +4942,7 @@ main (argc, argv)
 
       if (! verbose_flag)
 	{
-	  printf ("\nReport bugs to egcs-bugs@cygnus.com.\n");
+	  printf ("\nReport bugs to egcs-bugs@egcs.cygnus.com.\n");
 	  printf ("Please see the file BUGS (included with the sources) first.\n");
 	  
 	  exit (0);
@@ -5137,7 +5137,7 @@ main (argc, argv)
 
   if (print_help_list)
     {
-      printf ("\nReport bugs to egcs-bugs@cygnus.com.\n");
+      printf ("\nReport bugs to egcs-bugs@egcs.cygnus.com.\n");
       printf ("Please see the file BUGS (included with the sources) first.\n");
     }
   
diff --git a/gcc/gcc.texi b/gcc/gcc.texi
index 06551cd..547c7938 100644
--- a/gcc/gcc.texi
+++ b/gcc/gcc.texi
@@ -2194,13 +2194,13 @@ for improvement of GNU CC or GNU C++ are welcome in any case.
 @node Bug Lists
 @section Where to Report Bugs
 @cindex bug report mailing lists
-@kindex egcs-bugs@@cygnus.com
-Send bug reports for GNU C to @samp{egcs-bugs@@cygnus.com}.
+@kindex egcs-bugs@@egcs.cygnus.com
+Send bug reports for GNU C to @samp{egcs-bugs@@egcs.cygnus.com}.
 
-@kindex egcs-bugs@@cygnus.com
-@kindex egcs-bugs@@cygnus.com
+@kindex egcs-bugs@@egcs.cygnus.com
+@kindex egcs-bugs@@egcs.cygnus.com
 Send bug reports for GNU C++ and the C++ runtime libraries to
-@samp{egcs-bugs@@cygnus.com}.
+@samp{egcs-bugs@@egcs.cygnus.com}.
 
 Often people think of posting bug reports to the newsgroup instead of
 mailing them.  This appears to work, but it has one problem which can be
@@ -2259,7 +2259,7 @@ text if it is small. If the message is larger, you may compress it using
 @file{gzip}, @file{bzip2}, or @file{pkzip}. Please be aware that sending
 compressed files needs an additional binary-safe mechanism such as
 @code{MIME} or @code{uuencode}. There is a 40k message soft limit on the
-@samp{egcs-bugs@@cygnus.com} mailing list at the time of this writing
+@samp{egcs-bugs@@egcs.cygnus.com} mailing list at the time of this writing
 (August 1998).  However, if you can't reduce a bug report to less than
 that, post it anyway; it will be manually approved as long as it is
 compressed. Don't think that posting a URL to the code is better, we do
@@ -2493,7 +2493,7 @@ we should be able to reproduce the crash ourselves.
 
 If you would like to write bug fixes or improvements for the GNU C
 compiler, that is very helpful.  Send suggested fixes to the bug report
-mailing list, @code{egcs-bugs@@cygnus.com}.
+mailing list, @code{egcs-bugs@@egcs.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
@@ -2613,8 +2613,8 @@ ways to find it:
 @itemize @bullet
 @item
 Send a message to a suitable network mailing list.  First try
-@code{egcs-bugs@@cygnus.com}, and if that brings no response, try
-@code{egcs@@cygnus.com}.
+@code{egcs-bugs@@egcs.cygnus.com}, and if that brings no response, try
+@code{egcs@@egcs.cygnus.com}.
 
 @item
 Look in the service directory for someone who might help you for a fee.
@@ -2627,13 +2627,13 @@ GNU CC distribution.
 
 If you would like to help pretest GNU CC releases to assure they work
 well, or if you would like to work on improving GNU CC, please contact
-the maintainers at @code{egcs@@cygnus.com}.  A pretester should
+the maintainers at @code{egcs@@egcs.cygnus.com}.  A pretester should
 be willing to try to investigate bugs as well as report them.
 
 If you'd like to work on improvements, please ask for suggested projects
 or suggest your own ideas.  If you have already written an improvement,
 please tell us about it.  If you have not yet started work, it is useful
-to contact @code{egcs@@cygnus.com} before you start; the
+to contact @code{egcs@@egcs.cygnus.com} before you start; the
 maintainers may be able to suggest ways to make your extension fit in
 better with the rest of GNU CC and with other development plans.
 
diff --git a/gcc/invoke.texi b/gcc/invoke.texi
index e35ae49..20fb3d2 100644
--- a/gcc/invoke.texi
+++ b/gcc/invoke.texi
@@ -2452,7 +2452,7 @@ These two options are intended to be removed someday, once
 they have helped determine the efficacy of various
 approaches to improving loop optimizations.
 
-Please let us (@code{egcs@@cygnus.com} and @code{fortran@@gnu.org})
+Please let us (@code{egcs@@egcs.cygnus.com} and @code{fortran@@gnu.org})
 know how use of these options affects
 the performance of your production code.
 We're very interested in code that runs @emph{slower}
diff --git a/gcc/system.h b/gcc/system.h
index 0de7133..40efc9a 100644
--- a/gcc/system.h
+++ b/gcc/system.h
@@ -377,7 +377,7 @@ extern void abort ();
 #define abort()								\
 (fprintf (stderr,							\
 	  "%s:%d: Internal compiler error in function %s\n"             \
-	  "Please submit a full bug report to `egcs-bugs@cygnus.com'.\n"  \
+	  "Please submit a full bug report to `egcs-bugs@egcs.cygnus.com'.\n"  \
 	  "See <URL:http://egcs.cygnus.com/faq.html#bugreport> for details.\n", \
 	  __FILE__, __LINE__, __PRETTY_FUNCTION__),			\
  exit (FATAL_EXIT_CODE))