From 6a1d1088df3144fd467d9a706757c9b1cac3a55b Mon Sep 17 00:00:00 2001 From: Gerald Pfeifer Date: Fri, 15 Sep 2000 21:29:17 +0200 Subject: [PATCH] * BUGS: Remove file. From-SVN: r36445 --- gcc/BUGS | 27 --------------------------- gcc/ChangeLog | 4 ++++ 2 files changed, 4 insertions(+), 27 deletions(-) delete mode 100644 gcc/BUGS diff --git a/gcc/BUGS b/gcc/BUGS deleted file mode 100644 index 2d875a0..0000000 --- a/gcc/BUGS +++ /dev/null @@ -1,27 +0,0 @@ -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, -(2) where to send your bug report, and -(3) how to write a useful bug report and what information -it needs to have. - -There are three ways to read the Bugs section. - -(1) In a printed copy of the GCC manual. You can order one from the -Free Software Foundation; see the file ORDERS. But if you don't have -a copy on hand and you think you have found a bug, you shouldn't wait -to get a printed manual; you should read the section right away as -described below. - -(2) With Info. Start Emacs, do C-h i to enter Info, -then m gcc RET to get to the GCC manual, then m Bugs RET -to get to the section on bugs. Or use standalone Info in -a like manner. (Standalone Info is part of the Texinfo distribution.) - -(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 GCC FAQ, in which there are -additional instructions for submitting bug reports: - http://www.gnu.org/software/gcc/faq.html#bugreport diff --git a/gcc/ChangeLog b/gcc/ChangeLog index 4be01e7..5c1099e 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,7 @@ +2000-09-15 Gerald Pfeifer + + * BUGS: Remove file. + 2000-09-15 Jakub Jelinek * config/alpha/alpha.c (override_options): ev6 cache latencies -- 2.7.4