aboutsummaryrefslogtreecommitdiff
path: root/contrib/gcc/gcc.texi
diff options
context:
space:
mode:
Diffstat (limited to 'contrib/gcc/gcc.texi')
-rw-r--r--contrib/gcc/gcc.texi4
1 files changed, 2 insertions, 2 deletions
diff --git a/contrib/gcc/gcc.texi b/contrib/gcc/gcc.texi
index d2bbbb559020..8c08fa8b6d4c 100644
--- a/contrib/gcc/gcc.texi
+++ b/contrib/gcc/gcc.texi
@@ -2263,7 +2263,7 @@ convention, in which bug reports for tool ``foo'' are sent
to @samp{bug-foo@@gnu.org}, the address @samp{bug-gcc@@gnu.org}
may also be used; it will forward to the address given above.
-Please read @samp{<URL:http://www.gnu.org/software/gcc/faq.html#bugreport>} for
+Please read @samp{<URL:http://www.gnu.org/software/gcc/bugs.html>} for
bug reporting instructions before you post a bug report.
Often people think of posting bug reports to the newsgroup instead of
@@ -2287,7 +2287,7 @@ Boston, MA 02111-1307, USA
@cindex compiler bugs, reporting
You may find additional and/or more up-to-date instructions at
-@samp{<URL:http://www.gnu.org/software/gcc/faq.html#bugreport>}.
+@samp{<URL:http://www.gnu.org/software/gcc/bugs.html>}.
The fundamental principle of reporting bugs usefully is this:
@strong{report all the facts}. If you are not sure whether to state a