imported>La musique: Add a synonym of daily use

2023-08-10T15:32:24Z

Add a synonym of daily use

New page

'''Compilation error''' or '''compile error''' refers to a state when a [[compiler]] fails to compile a piece of [[computer program]] [[source code]], either due to errors in the code, or, more unusually, due to errors in the compiler itself. A compilation error message often helps [[computer programmer|programmers]] [[debugging]] the source code. Although the definitions of compilation and [[Interpreter (computing)|interpretation]] can be vague, generally compilation errors only refer to static compilation and not [[dynamic compilation]]. However, dynamic compilation can still technically have compilation errors,{{Citation needed|date=October 2018}} although many programmers and sources may identify them as [[Runtime error detection|run-time errors]]. Most [[Just in time compiler|just-in-time compilers]], such as the [[Chrome V8|Javascript V8 engine]], ambiguously refer to compilation errors as [[syntax error]]s since they check for them at [[Run time (program lifecycle phase)|run time]].<ref>{{Cite web|url=https://nodejs.org/api/errors.html#errors_class_syntaxerror|title=Errors {{!}} Node.js v7.9.0 Documentation|website=nodejs.org|language=en|access-date=2017-04-14}}</ref><ref>{{Cite web|url=https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/SyntaxError|title=SyntaxError|website=Mozilla Developer Network|language=en-US|access-date=2017-04-14}}</ref>

== Examples ==
=== Common C++ compilation errors ===
* Undeclared identifier, e.g.:
<code>doy.cpp: In function `int main()':
doy.cpp:25: `DayOfYear' undeclared (first use this function)</code><ref name="common-c++-compiler-and-linker-errors">{{cite web|title=Common C++ Compiler and Linker Errors|url=http://www.csee.umbc.edu/courses/undergraduate/341/misc/CommonErrors.shtml|access-date=2008-02-12|archive-url=https://web.archive.org/web/20080216062430/http://www.csee.umbc.edu/courses/undergraduate/341/misc/CommonErrors.shtml|archive-date=2008-02-16|url-status=dead}}</ref>

This means that the variable "DayOfYear" is trying to be used before being declared.

* Common function undeclared, e.g.:
<code>xyz.cpp: In function `int main()': xyz.cpp:6: `cout' undeclared (first use this function)</code><ref name="common-c++-compiler-and-linker-errors"/>

This means that the programmer most likely forgot to include ''iostream''.

* Parse error, e.g.:
<code>somefile.cpp:24: parse error before `something'</code><ref name="compiler-linker-and-run-time-errors">{{cite web|title=Compiler, Linker and Run-Time Errors|url=http://www.cs.bu.edu/teaching/cpp/debugging/errors/}}</ref>

This could mean that a semi-colon is missing at the end of the previous statement.

=== Internal Compiler Errors ===
An internal compiler error (commonly abbreviated as ICE) is an error that occurs not due to erroneous source code, but rather due to a bug in the compiler itself. They can sometimes be worked around by making small, insignificant changes to the source code around the line indicated by the error (if such a line is indicated at all),<ref>{{Cite web|url=http://wiki.c2.com/?CompilerBug|title=Compiler Bug|last=Cunningham|first=Ward|date=2010-03-18|website=WikiWikiWeb|access-date=2017-04-14}}</ref>{{better source needed|date=February 2019}} but sometimes larger changes must be made, such as [[Code refactoring|refactoring]] the code, to avoid certain constructs. Using a different compiler or different version of the compiler may solve the issue and be an acceptable solution in some cases. When an internal compiler error is reached many compilers do not output a standard error, but instead output a shortened version, with additional files attached, which are only provided for internal compiler errors. This is in order to insure that the program doesn't crash when logging the error, which would make solving the error nigh impossible. The additional files attached for internal compiler errors usually have special formats that they save as, such as <code>.dump</code> for [[Java (programming language)|Java]]. These formats are generally more difficult to analyze than regular files, but can still have very helpful information for solving the bug causing the crash.<ref>{{Cite web|url=http://jagadesh4java.blogspot.com/2014/09/analyzing-jvm-crash.html|title=Analyzing a JVM Crash|last=జగదేశ్|access-date=2017-04-15}}</ref>

Example of an internal compiler error:
<pre>somefile.c:1001: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://bugs.gentoo.org/> for instructions.</pre>

== References ==
{{reflist}}

[[Category:Debugging]]
[[Category:Computer errors]]

Compilation error - Revision history

imported>La musique: Add a synonym of daily use