]> gcc.gnu.org Git - gcc.git/blame - gcc/BUGS
cpplib.c (macroexpand): Correct off-by-one error in handling of escapes.
[gcc.git] / gcc / BUGS
CommitLineData
667d88ab
RK
1If you think you may have found a bug in GNU CC, please
2read the Bugs section of the GCC manual for advice on
3
4(1) how to tell when to report a bug,
5(2) where to send your bug report, and
6(2) how to write a useful bug report and what information
7it needs to have.
8
9There are three ways to read the Bugs section.
10
11(1) In a printed copy of the GCC manual. You can order one from the
12Free Software Foundation; see the file ORDERS. But if you don't have
13a copy on hand and you think you have found a bug, you shouldn't wait
14to get a printed manual; you should read the section right away as
15described below.
16
17(2) With Info. Start Emacs, do C-h i to enter Info,
18then m gcc RET to get to the GCC manual, then m Bugs RET
19to get to the section on bugs. Or use standalone Info in
20a like manner. (Standalone Info is part of the Texinfo distribution.)
21
22(3) By hand. Search for the chapter "Reporting Bugs" in gcc.texi, or
23 cat /usr/local/info/gcc* | more "+/^File: emacs, Node: Bugs,"
This page took 0.151375 seconds and 5 git commands to generate.