Commit e547bb67 by Jeff Law

More mail address and web address updates.

From-SVN: r28616
parent b3967ec4
...@@ -2,7 +2,7 @@ This directory has been obsoleted for egcs snapshots and CVS access. ...@@ -2,7 +2,7 @@ This directory has been obsoleted for egcs snapshots and CVS access.
Instead check out the toplevel "wwwdocs" as a sibling of your egcs Instead check out the toplevel "wwwdocs" as a sibling of your egcs
tree or read these files via the egcs web site tree or read these files via the egcs web site
http://egcs.cygnus.com http://www.gnu.org/software/gcc/
Copies of the relevant files will be copied into this directory for Copies of the relevant files will be copied into this directory for
......
If you think you may have found a bug in GNU CC, please If you think you may have found a bug in GCC, please
read the Bugs section of the GCC manual for advice on read the Bugs section of the GCC manual for advice on
(1) how to tell when to report a bug, (1) how to tell when to report a bug,
...@@ -22,6 +22,6 @@ a like manner. (Standalone Info is part of the Texinfo distribution.) ...@@ -22,6 +22,6 @@ a like manner. (Standalone Info is part of the Texinfo distribution.)
(3) By hand. Search for the chapter "Reporting Bugs" in gcc.texi, or (3) By hand. Search for the chapter "Reporting Bugs" in gcc.texi, or
cat /usr/local/info/gcc* | more "+/^File: gcc.info, Node: Bugs," cat /usr/local/info/gcc* | more "+/^File: gcc.info, Node: Bugs,"
You may also want to take a look at the EGCS FAQ, in which there are You may also want to take a look at the GCC FAQ, in which there are
additional instructions for submitting bug reports: additional instructions for submitting bug reports:
http://egcs.cygnus.com/faq.html#bugreport http://www.gnu.org/software/gcc/faq.html#bugreport
...@@ -364,7 +364,7 @@ my_friendly_abort (i) ...@@ -364,7 +364,7 @@ my_friendly_abort (i)
error ("Internal compiler error %d.", i); error ("Internal compiler error %d.", i);
error ("Please submit a full bug report."); error ("Please submit a full bug report.");
fatal ("See <URL:http://egcs.cygnus.com/faq.html#bugreport> for instructions."); fatal ("See <URL:http://www.gnu.org/software/gcc/faq.html#bugreport> for instructions.");
} }
void void
......
...@@ -33,7 +33,7 @@ is expected to contain documentation that is most consistent with the ...@@ -33,7 +33,7 @@ is expected to contain documentation that is most consistent with the
An online, "live" version of this document (derived directly from An online, "live" version of this document (derived directly from
the mainline, development version of `g77' within `egcs') is available the mainline, development version of `g77' within `egcs') is available
via `http://egcs.cygnus.com/onlinedocs/g77_bugs.html'. Follow the via `http://www.gnu.org/software/gcc/onlinedocs/g77_bugs.html'. Follow the
"Known Bugs" link. "Known Bugs" link.
For information on bugs that might afflict people who configure, For information on bugs that might afflict people who configure,
......
...@@ -64,7 +64,7 @@ about previous `g77' versions up-to-date. ...@@ -64,7 +64,7 @@ about previous `g77' versions up-to-date.
An online, "live" version of this document (derived directly from An online, "live" version of this document (derived directly from
the mainline, development version of `g77' within `egcs') is available the mainline, development version of `g77' within `egcs') is available
at `http://egcs.cygnus.com/onlinedocs/g77_news.html'. at `http://www.gnu.org/software/gcc/onlinedocs/g77_news.html'.
The following information was last updated on 1999-07-08: The following information was last updated on 1999-07-08:
......
...@@ -79,7 +79,7 @@ An online, ``live'' version of this document ...@@ -79,7 +79,7 @@ An online, ``live'' version of this document
(derived directly from the mainline, development version (derived directly from the mainline, development version
of @code{g77} within @code{egcs}) of @code{g77} within @code{egcs})
is available via is available via
@uref{http://egcs.cygnus.com/onlinedocs/g77_bugs.html}. @uref{http://www.gnu.org/software/gcc/onlinedocs/g77_bugs.html}.
Follow the ``Known Bugs'' link. Follow the ``Known Bugs'' link.
@ifset DOC-G77 @ifset DOC-G77
......
...@@ -21,7 +21,7 @@ search for the string TBD. ...@@ -21,7 +21,7 @@ search for the string TBD.
If you want to help by working on one or more of these items, If you want to help by working on one or more of these items,
email me at @email{@value{email-burley}}. email me at @email{@value{email-burley}}.
If you're planning to do more than just research issues and offer comments, If you're planning to do more than just research issues and offer comments,
see @uref{http://egcs.cygnus.com/contribute.html} for steps you might see @uref{http://www.gnu.org/software/contribute.html} for steps you might
need to take first. need to take first.
@menu @menu
......
...@@ -146,7 +146,7 @@ An online, ``live'' version of this document ...@@ -146,7 +146,7 @@ An online, ``live'' version of this document
(derived directly from the mainline, development version (derived directly from the mainline, development version
of @code{g77} within @code{egcs}) of @code{g77} within @code{egcs})
is available at is available at
@uref{http://egcs.cygnus.com/onlinedocs/g77_news.html}. @uref{http://www.gnu.org/software/gcc/onlinedocs/g77_news.html}.
@end ifclear @end ifclear
The following information was last updated on @value{last-update-news}: The following information was last updated on @value{last-update-news}:
......
...@@ -2681,13 +2681,13 @@ GCC distribution. ...@@ -2681,13 +2681,13 @@ GCC distribution.
If you would like to help pretest GCC releases to assure they work If you would like to help pretest GCC releases to assure they work
well, or if you would like to work on improving GCC, please contact well, or if you would like to work on improving GCC, please contact
the maintainers at @code{egcs@@egcs.cygnus.com}. A pretester should the maintainers at @code{gcc@@gcc.gnu.org}. A pretester should
be willing to try to investigate bugs as well as report them. 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 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, 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 please tell us about it. If you have not yet started work, it is useful
to contact @code{egcs@@egcs.cygnus.com} before you start; the to contact @code{gcc@@gcc.gnu.org} before you start; the
maintainers may be able to suggest ways to make your extension fit in maintainers may be able to suggest ways to make your extension fit in
better with the rest of GCC and with other development plans. better with the rest of GCC and with other development plans.
......
...@@ -399,7 +399,7 @@ extern void fatal PVPROTO((const char *, ...)) ATTRIBUTE_PRINTF_1 ATTRIBUTE_NORE ...@@ -399,7 +399,7 @@ extern void fatal PVPROTO((const char *, ...)) ATTRIBUTE_PRINTF_1 ATTRIBUTE_NORE
#else #else
#define abort() fatal ("Internal compiler error in `%s', at %s:%d\n" \ #define abort() fatal ("Internal compiler error in `%s', at %s:%d\n" \
"Please submit a full bug report.\n" \ "Please submit a full bug report.\n" \
"See <URL:http://egcs.cygnus.com/faq.html#bugreport> for instructions.", \ "See <URL:http://www.gnu.org/software/gcc/faq.html#bugreport> for instructions.", \
__PRETTY_FUNCTION__, trim_filename (__FILE__), __LINE__) __PRETTY_FUNCTION__, trim_filename (__FILE__), __LINE__)
#endif /* recent gcc */ #endif /* recent gcc */
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment