diff options
author | Martin v. Löwis <loewis@gcc.gnu.org> | 2000-04-04 22:54:44 +0000 |
---|---|---|
committer | Martin v. Löwis <loewis@gcc.gnu.org> | 2000-04-04 22:54:44 +0000 |
commit | 501a481953e55fabdc06e43dcab9972b7113bd15 (patch) | |
tree | b3aa9ca5feb546e55eb1d899ecbcb2212b4da4d7 /gcc/gcc.texi | |
parent | ace8b0159829f653eac9c7a79fa72d2d0905508f (diff) | |
download | gcc-501a481953e55fabdc06e43dcab9972b7113bd15.zip gcc-501a481953e55fabdc06e43dcab9972b7113bd15.tar.gz gcc-501a481953e55fabdc06e43dcab9972b7113bd15.tar.bz2 |
Makefile (gccbug): New target.
* Makefile (gccbug): New target.
(doc): Depend on it.
* gcc.texi (Bugs): Link subnodes.
(gccbug): New node.
* gccbug.in (CATEGORIES): Remove gc, host, profiling, libgcc.
Document severities, priorities, and classes in bug form.
* ChangeLog: Replace leading spaces with tabs.
From-SVN: r32915
Diffstat (limited to 'gcc/gcc.texi')
-rw-r--r-- | gcc/gcc.texi | 140 |
1 files changed, 136 insertions, 4 deletions
diff --git a/gcc/gcc.texi b/gcc/gcc.texi index b59fc65..a12dd35 100644 --- a/gcc/gcc.texi +++ b/gcc/gcc.texi @@ -2156,12 +2156,13 @@ information that makes for fixing the bug. * Criteria: Bug Criteria. Have you really found a bug? * Where: Bug Lists. Where to send your bug report. * Reporting: Bug Reporting. How to report a bug effectively. +* GNATS: gccbug. You can use a bug reporting tool. * Patches: Sending Patches. How to send a patch for GCC. * Known: Trouble. Known problems. * Help: Service. Where to ask for help. @end menu -@node Bug Criteria +@node Bug Criteria,Bug Lists,,Bugs @section Have You Found a Bug? @cindex bug criteria @@ -2228,7 +2229,7 @@ If you are an experienced user of one of the languages GCC supports, your suggestions for improvement of GCC are welcome in any case. @end itemize -@node Bug Lists +@node Bug Lists,Bug Reporting,Bug Criteria,Bugs @section Where to Report Bugs @cindex bug report mailing lists @kindex gcc-bugs@@gcc.gnu.org or bug-gcc@@gnu.org @@ -2257,7 +2258,7 @@ Free Software Foundation Boston, MA 02111-1307, USA @end example -@node Bug Reporting +@node Bug Reporting,gccbug,Bug Lists,Bugs @section How to Report Bugs @cindex compiler bugs, reporting @@ -2517,7 +2518,138 @@ unless we have an identical system---and if we do have one, we should be able to reproduce the crash ourselves. @end itemize -@node Sending Patches,, Bug Reporting, Bugs +@node gccbug,Sending Patches, Bug Reporting, Bugs +@section The gccbug script +@cindex gccbug script + +To simplify creation of bug reports, and to allow better tracking of +reports, we use the GNATS bug tracking system. Part of that system is +the @code{gccbug} script. This is a Unix shell script, so you need a +shell to run it. It is normally installed in the same directory where +@code{gcc} is installed. + +The gccbug script is derived from send-pr, @pxref{using +send-pr,,Creating new Problem Reports,send-pr,Reporting Problems}. When +invoked, it starts a text editor so you can fill out the various fields +of the report. When the you quit the editor, the report is automatically +send to the bug reporting address. + +A number of fields in this bug report form are specific to GCC, and are +explained here. + +@table @code + +@cindex @code{Category} field +@cindex @code{>Category:} +@item >Category: +The category of a GCC problem can be one of the following: + +@table @code +@item c +A problem with the C compiler proper. +driver. + +@item c++ +A problem with the C++ compiler. +driver. + +@item fortran +A problem with the Fortran 77. + +@item java +A problem with the Java compiler. + +@item objc +A problem with the Objective C compiler. + +@item libstdc++ +A problem with the C++ standard library. + +@item libf2c +A problem with the Fortran 77 library. + +@item libobjc +A problem with the Objective C library. + +@item optimization +The problem occurs only when generating optimized code. + +@item debug +The problem occurs only when generating code for debugging. + +@item target +The problem is specific to the target architecture. + +@item middle-end +The problem is independent from target architecture and programming +language. + +@item other +It is a problem in some other part of the GCC software. + +@item web +There is a problem with the GCC home page. + +@end table + +@cindex @code{Class} field +@cindex @code{>Class:} +@item >Class: +The class of a problem can be one of the following: + +@table @code +@cindex @emph{doc-bug} class +@item doc-bug +A problem with the documentation. + +@cindex @emph{accepts-illegal} class +@item accepts-illegal +GCC fails to reject erroneous code. + +@cindex @emph{rejects-legal} class +@item rejects-legal +GCC gives an error message for correct code. + +@cindex @emph{wrong-code} class +@item wrong-code +The machine code generated by gcc is incorrect. + +@cindex @emph{ice-on-legal-code} class +@item ice-on-legal-code +GCC gives an Internal Compiler Error (ICE) for correct code. + +@cindex @emph{ice-on-illegal-code} class +@item ice-on-illegal-code +GCC gives an ICE instead of reporting an error + +@cindex @emph{pessimizes-code} class +@item pessimizes-code +GCC misses an important optimization opportunity. + +@cindex @emph{sw-bug} class +@item sw-bug +A general product problem. (@samp{sw} stands for ``software''.) + +@cindex @emph{change-request} class +@item change-request +A request for a change in behavior, etc. + +@cindex @emph{support} class +@item support +A support problem or question. + +@cindex @emph{duplicate} class +@item duplicate (@var{pr-number}) +Duplicate PR. @var{pr-number} should be the number of the original PR. + +@noindent +The default is @samp{sw-bug}. +@sp 1 +@end table + +@end table + +@node Sending Patches,, gccbug, Bugs @section Sending Patches for GCC If you would like to write bug fixes or improvements for the GNU C |