Lines Matching full:bug
22 <li><a href="#detailed">Detailed bug reporting instructions</a></li>
23 <li><a href="#gnat">Detailed bug reporting instructions for GNAT</a></li>
24 <li><a href="#pch">Detailed bug reporting instructions when using a precompiled header</a></li>
55 <p>The main purpose of a bug report is to enable us to fix the bug. The
59 <p>Before you report a bug, please check the
62 If you want to report a bug with versions of GCC before 3.1 we strongly
67 anything wrong with your code that could be the cause instead of a bug
70 <h2>Summarized bug reporting instructions</h2>
72 <p>After this summary, you'll find detailed bug reporting
78 <p>Please include in your bug report all of the following items, the first
85 <li>the complete command line that triggers the bug;</li>
88 bug, generated by adding <code>-save-temps</code> to the complete
89 compilation command, or, in the case of a bug report for the GNAT front end,
97 out of the bug report (see above)</li>
105 exact output mentioned in the bug report (e.g., a snippet with just
106 a few lines around the one that <b>apparently</b> triggers the bug,
112 duplicate the bug, haven't you? :-)</li>
117 not of a compiler bug (sorry)</li>
119 <li>E-mail messages that complement previous, incomplete bug
120 reports. Post a new, self-contained, full bug report instead, if
121 possible as a follow-up to the original bug report</li>
127 <li>Duplicate bug reports, or reports of bugs already fixed in the
132 separate projects, with separate mailing lists and different bug
145 <p>Please submit your bug report directly to the
146 <a href="http://gcc.gnu.org/bugzilla/">GCC bug database</a>.
147 Alternatively, you can use the <code>gccbug</code> script that mails your bug
148 report to the bug database.
153 <h2><a name="detailed">Detailed bug reporting instructions</a></h2>
173 preprocessor output in your bug report, even if the source code is
178 (i) if you've found a bug in the preprocessor, (ii) if you've reduced
180 (iii) if the bug appears only when using precompiled headers. If you
186 it in the bug report, although you may want to post parts of it to
192 bug report in order to tell who should take care of it. A meaningful
196 need just a single file to reproduce the bug (the .i/.ii/.f preprocessed
198 volunteers' jobs harder. Only when your bug report requires multiple
204 the body of your bug report as plain text, even if needlessly
207 <p>If you fail to supply enough information for a bug report to be
209 information (or just ignore your bug report, if they're in a bad day,
211 post the additional information to the bug reporting mailing list, not
214 supplied in the incomplete bug report (including the preprocessor
215 output), so that the new bug report is self-contained.</p>
217 <h2><a name="gnat">Detailed bug reporting instructions for GNAT</a></h2>
219 <p>See the <a href="#detailed">previous section</a> for bug reporting
222 <p>Bug reports have to contain at least the following information in
230 triggering the bug
233 <li>a collection of source files for reproducing the bug,
248 <p>If you report a bug which causes the compiler to print a bug box,
249 include that bug box in your report, and do not forget to send all the
250 source files listed after the bug box along with your report.</p>
253 sources (unless you have to report a bug in <code>gnatprep</code>).</p>
260 <h2><a name="pch">Detailed bug reporting instructions when using a
263 <p>If you're encountering a bug when using a precompiled header, the
265 the same GCC command again. If the bug happens again, the bug doesn't
269 <p>If you've found a bug while <i>building</i> a precompiled header
273 <p>If you've found a real precompiled header bug, what we'll need to
290 them, this document might save people the effort of writing a bug report
291 when the bug is already well-known.</p>
293 <p>There are many reasons why a reported bug doesn't get fixed.
414 <p>It is not always a bug in the compiler, if code which "worked" in a
428 <a href="http://gcc.gnu.org/PR323">most often reported non-bug</a>.</dt>
450 <p>This is not a bug in the compiler, but an inherent limitation of
780 to a bug-fix release of the same version of the compiler; bug-fix
786 component of the two- or three-part version number. A minor (bug-fix)
788 3.2 and 3.3 are major releases, while 3.3.1 and 3.3.2 are bug-fix releases