diff options
author | Niklas Hallqvist <niklas@cvs.openbsd.org> | 1995-12-20 01:06:22 +0000 |
---|---|---|
committer | Niklas Hallqvist <niklas@cvs.openbsd.org> | 1995-12-20 01:06:22 +0000 |
commit | c482518380683ee38d14024c1e362a0d681cf967 (patch) | |
tree | e69b4f6d3fee3aced20a41f3fdf543fc1c77fb5d /gnu/usr.bin/gcc/BUGS | |
parent | 76a62188d0db49c65b696d474c855a799fd96dce (diff) |
FSF GCC version 2.7.2
Diffstat (limited to 'gnu/usr.bin/gcc/BUGS')
-rw-r--r-- | gnu/usr.bin/gcc/BUGS | 23 |
1 files changed, 23 insertions, 0 deletions
diff --git a/gnu/usr.bin/gcc/BUGS b/gnu/usr.bin/gcc/BUGS new file mode 100644 index 00000000000..dc023cffc51 --- /dev/null +++ b/gnu/usr.bin/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 Emacs 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," |