diff options
| author | Richard Kenner <kenner@gcc.gnu.org> | 1997-04-23 09:34:56 -0400 |
|---|---|---|
| committer | Richard Kenner <kenner@gcc.gnu.org> | 1997-04-23 09:34:56 -0400 |
| commit | 667d88ab01b91a31ebdeea0d2e373f273ba3b443 (patch) | |
| tree | 0469d9f4ba96c8fc40635b91db56159793c59020 /gcc | |
| parent | 1101bba443100290b7b99c7e64a63f638219c2cb (diff) | |
| download | gcc-667d88ab01b91a31ebdeea0d2e373f273ba3b443.zip gcc-667d88ab01b91a31ebdeea0d2e373f273ba3b443.tar.gz gcc-667d88ab01b91a31ebdeea0d2e373f273ba3b443.tar.bz2 | |
entered into RCS
From-SVN: r13961
Diffstat (limited to 'gcc')
| -rw-r--r-- | gcc/BUGS | 23 |
1 files changed, 23 insertions, 0 deletions
diff --git a/gcc/BUGS b/gcc/BUGS new file mode 100644 index 0000000..33c9386 --- /dev/null +++ b/gcc/BUGS @@ -0,0 +1,23 @@ +If you think you may have found a bug in GNU CC, 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 +(2) 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: emacs, Node: Bugs," |