Instead check out the toplevel "wwwdocs" as a sibling of your egcs
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
-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
(1) how to tell when to report a bug,
(3) By hand. Search for the chapter "Reporting Bugs" in gcc.texi, or
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:
- http://egcs.cygnus.com/faq.html#bugreport
+ http://www.gnu.org/software/gcc/faq.html#bugreport
error ("Internal compiler error %d.", i);
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
An online, "live" version of this document (derived directly from
the mainline, development version of `g77' within `egcs') is available
-via `http://egcs.cygnus.com/onlinedocs/g77_bugs.html'. Follow the
+via `http://www.gnu.org/software/gcc/onlinedocs/g77_bugs.html'. Follow the
"Known Bugs" link.
For information on bugs that might afflict people who configure,
An online, "live" version of this document (derived directly from
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:
(derived directly from the mainline, development version
of @code{g77} within @code{egcs})
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.
@ifset DOC-G77
If you want to help by working on one or more of these items,
email me at @email{@value{email-burley}}.
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.
@menu
(derived directly from the mainline, development version
of @code{g77} within @code{egcs})
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
The following information was last updated on @value{last-update-news}:
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
-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.
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@@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
better with the rest of GCC and with other development plans.
#else
#define abort() fatal ("Internal compiler error in `%s', at %s:%d\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__)
#endif /* recent gcc */