PATCH: gcc.texi and GNATS

[Gerald Pfeifer <pfeifer at dbai dot tuwien dot ac dot at>]

I'm going to install this both on mainline and the branch. This is another
step in reducing the duplications between web and texinfo documentation;
this time the web stuff should be authoritative.

(And Joseph surely will like this. ;-) )

Gerald

2001-05-17  Gerald Pfeifer  <pfeifer@dbai.tuwien.ac.at>

	* gcc.texi (gccbug): Refer to the web pages for detailed information
	on GNATS.

Index: gcc.texi
===================================================================
RCS file: /cvs/gcc/egcs/gcc/gcc.texi,v
retrieving revision 1.75.2.10
diff -u -3 -p -r1.75.2.10 gcc.texi
--- gcc.texi	2001/05/13 21:36:16	1.75.2.10
+++ gcc.texi	2001/05/17 11:17:23
@@ -2616,119 +2616,8 @@ of the report. When the you quit the edi
 send to the bug reporting address.

 A number of fields in this bug report form are specific to GCC, and are
-explained here.
+explained at @uref{http://gcc.gnu.org/gnats.html}.

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