📄 bugs.html
字号:
<html lang="en">
<head>
<title>Using the GNU Compiler Collection (GCC)</title>
<meta http-equiv="Content-Type" content="text/html">
<meta name="description" content="Using the GNU Compiler Collection (GCC)">
<meta name="generator" content="makeinfo 4.3">
<link href="http://www.gnu.org/software/texinfo/" rel="generator-home">
<!--
Copyright © 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998,
1999, 2000, 2001, 2002, 2003 Free Software Foundation, Inc.
<p>Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.2 or
any later version published by the Free Software Foundation; with the
Invariant Sections being "GNU General Public License" and "Funding
Free Software", the Front-Cover texts being (a) (see below), and with
the Back-Cover Texts being (b) (see below). A copy of the license is
included in the section entitled "GNU Free Documentation License".
<p>(a) The FSF's Front-Cover Text is:
<p>A GNU Manual
<p>(b) The FSF's Back-Cover Text is:
<p>You have freedom to copy and modify this GNU Manual, like GNU
software. Copies published by the Free Software Foundation raise
funds for GNU development.-->
</head>
<body>
<div class="node">
<p>
Node:<a name="Bugs">Bugs</a>,
Next:<a rel="next" accesskey="n" href="Service.html#Service">Service</a>,
Previous:<a rel="previous" accesskey="p" href="Trouble.html#Trouble">Trouble</a>,
Up:<a rel="up" accesskey="u" href="index.html#Top">Top</a>
<hr><br>
</div>
<h2 class="chapter">Reporting Bugs</h2>
<p>Your bug reports play an essential role in making GCC reliable.
<p>When you encounter a problem, the first thing to do is to see if it is
already known. See <a href="Trouble.html#Trouble">Trouble</a>. If it isn't known, then you should
report the problem.
<p>Reporting a bug may help you by bringing a solution to your problem, or
it may not. (If it does not, look in the service directory; see
<a href="Service.html#Service">Service</a>.) In any case, the principal function of a bug report is
to help the entire community by making the next version of GCC work
better. Bug reports are your contribution to the maintenance of GCC.
<p>Since the maintainers are very overloaded, we cannot respond to every
bug report. However, if the bug has not been fixed, we are likely to
send you a patch and ask you to tell us whether it works.
<p>In order for a bug report to serve its purpose, you must include the
information that makes for fixing the bug.
<ul class="menu">
<li><a accesskey="1" href="Bug-Criteria.html#Bug%20Criteria">Criteria</a>: Have you really found a bug?
<li><a accesskey="2" href="Bug-Lists.html#Bug%20Lists">Where</a>: Where to send your bug report.
<li><a accesskey="3" href="Bug-Reporting.html#Bug%20Reporting">Reporting</a>: How to report a bug effectively.
<li><a accesskey="4" href="gccbug.html#gccbug">GNATS</a>: You can use a bug reporting tool.
<li><a accesskey="5" href="Trouble.html#Trouble">Known</a>: Known problems.
<li><a accesskey="6" href="Service.html#Service">Help</a>: Where to ask for help.
</ul>
</body></html>
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -