head	1.1;
access;
symbols
	gcc-2_8_1-990325:1.1
	gcc-2_8_1-990319:1.1
	gcc-2_8_1-990302:1.1
	gcc_2_8_1-990302:1.1
	gcc_2_8_1-990222:1.1
	gcc-2_8_1-990109:1.1
	gcc-2_8_1-981210:1.1
	gcc-2_8_1-981208:1.1
	gcc-2_8_1-980929:1.1
	gcc_2_8_1-980929:1.1
	gcc-2_8_1-980928:1.1
	gcc-2_8_1-980813:1.1
	gcc-2_8_1-980811:1.1
	gcc-2_8_1-980718:1.1
	gcc-2_8_1-980705:1.1
	gcc-2_8_1-980627:1.1
	gcc-2_8_1-980609:1.1
	gcc-2_8_1-980608:1.1
	gcc-2_8_1-980529:1.1
	gcc-2_8_1-980525:1.1
	gcc-2_8_1-980513:1.1
	gcc-2_8_1-980502:1.1
	gcc-2_8_1-980402:1.1
	gcc-2_8_1-980426:1.1
	gcc-2_8_1-980419:1.1
	gcc-2_8_1-980413:1.1
	gcc-2_8_1-980412:1.1
	gcc-2_8_1-980407:1.1
	gcc-2_8_1-980401:1.1
	gcc_2_8_1-980315:1.1
	gcc-2_8_1-RELEASE:1.1;
locks; strict;
comment	@# @;


1.1
date	97.04.23.13.34.56;	author kenner;	state Exp;
branches;
next	;


desc
@If you think you may have found a bug in GNU CC, please
@


1.1
log
@entered into RCS
@
text
@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,"
@
