OpenE2K/gcc
2
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

* BUGS: Remove file.

Browse Source 
From-SVN: r36445
This commit is contained in:
Gerald Pfeifer 2000-09-15 21:29:17 +02:00 committed by Gerald Pfeifer
parent 54f5c4b098
commit 6a1d1088df
2 changed files with 4 additions and 27 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

27
gcc/BUGS
View File

@ -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

4
gcc/ChangeLog
View File

@ -1,3 +1,7 @@
2000-09-15 Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
* BUGS: Remove file.
2000-09-15 Jakub Jelinek <jakub@redhat.com>
* config/alpha/alpha.c (override_options): ev6 cache latencies