📄 bug-criteria.html

📁 自己收集的linux入门到学懂高级编程书集包括linux程序设计第三版
💻 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.6"><!--Copyright &copy; 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998,1999, 2000, 2001, 2002, 2003, 2004 Free Software Foundation, Inc.   <p>Permission is granted to copy, distribute and/or modify this documentunder the terms of the GNU Free Documentation License, Version 1.2 orany later version published by the Free Software Foundation; with theInvariant Sections being "GNU General Public License" and "FundingFree Software", the Front-Cover texts being (a) (see below), and withthe Back-Cover Texts being (b) (see below).  A copy of the license isincluded 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.--><meta http-equiv="Content-Style-Type" content="text/css"><style type="text/css"><!--  pre.display { font-family:inherit }  pre.format  { font-family:inherit }  pre.smalldisplay { font-family:inherit; font-size:smaller }  pre.smallformat  { font-family:inherit; font-size:smaller }  pre.smallexample { font-size:smaller }  pre.smalllisp    { font-size:smaller }--></style></head><body><div class="node"><p>Node:&nbsp;<a name="Bug%20Criteria">Bug Criteria</a>,Next:&nbsp;<a rel="next" accesskey="n" href="Bug-Reporting.html#Bug%20Reporting">Bug Reporting</a>,Up:&nbsp;<a rel="up" accesskey="u" href="Bugs.html#Bugs">Bugs</a><hr><br></div><h3 class="section">Have You Found a Bug?</h3><p>If you are not sure whether you have found a bug, here are some guidelines:     <ul><li>If the compiler gets a fatal signal, for any input whatever, that is acompiler bug.  Reliable compilers never crash.     <li>If the compiler produces invalid assembly code, for any input whatever(except an <code>asm</code> statement), that is a compiler bug, unless thecompiler reports errors (not just warnings) which would ordinarilyprevent the assembler from being run.     <li>If the compiler produces valid assembly code that does not correctlyexecute the input source code, that is a compiler bug.     <p>However, you must double-check to make sure, because you may have aprogram whose behavior is undefined, which happened by chance to givethe desired results with another C or C++ compiler.     <p>For example, in many nonoptimizing compilers, you can write <code>x;</code>at the end of a function instead of <code>return x;</code>, with the sameresults.  But the value of the function is undefined if <code>return</code>is omitted; it is not a bug when GCC produces different results.     <p>Problems often result from expressions with two increment operators,as in <code>f (*p++, *p++)</code>.  Your previous compiler might haveinterpreted that expression the way you intended; GCC mightinterpret it another way.  Neither compiler is wrong.  The bug isin your code.     <p>After you have localized the error to a single source line, it shouldbe easy to check for these things.  If your program is correct andwell defined, you have found a compiler bug.     </p><li>If the compiler produces an error message for valid input, that is acompiler bug.     <li>If the compiler does not produce an error message for invalid input,that is a compiler bug.  However, you should note that your idea of"invalid input" might be my idea of "an extension" or "supportfor traditional practice".     <li>If you are an experienced user of one of the languages GCC supports, yoursuggestions for improvement of GCC are welcome in any case. </ul>   </body></html>
⌨️ 快捷键说明

复制代码 Ctrl + C
搜索代码 Ctrl + F
全屏模式 F11
切换主题 Ctrl + Shift + D
显示快捷键 ?
增大字号 Ctrl + =
减小字号 Ctrl + -