Compilation error

Compilation 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 programmers debugging the source code. Although the definitions of compilation and interpretation can be vague, generally compilation errors only refer to static compilation and not dynamic compilation. However, it is important to note that dynamic compilation can still technically have compilation errors, although many programmers and sources may identify them as run-time errors. Most just-in-time compilers, such as the Javascript V8 engine, ambiguously refer to compilation errors as syntax errors since they check for them at run time.[1][2]

Examples

Common C++ compilation errors
  • Undeclared identifier, e.g.:

doy.cpp: In function `int main()': doy.cpp:25: `DayOfYear' undeclared (first use this function)[3]

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

  • Common function undeclared, e.g.:

xyz.cpp: In function `int main()': xyz.cpp:6: `cout' undeclared (first use this function)[3]

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

  • Parse error, e.g.:

somefile.cpp:24: parse error before `something'[4]

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),[5] but sometimes larger changes must be made, such as 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 .dump for 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.[6]

Example of an internal compiler error:

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.
gollark: It apparently makes brute force take O(sqrt n) time somehow.
gollark: Yes, something something grover's algorithm.
gollark: This is... interesting. I would run it through some sort of automatic formatter tool.
gollark: These are designed to work best on general purpose CPUs - to prevent using dedicated hardware to accelerate bruteforce - and to have a tunable time requirement.
gollark: But this doesn't really mean much. Sanely designed systems now will be using stuff like scrypt/bcrypt/argon2.

References
  1. "Errors | Node.js v7.9.0 Documentation". nodejs.org. Retrieved 2017-04-14.
  2. "SyntaxError". Mozilla Developer Network. Retrieved 2017-04-14.
  3. "Common C++ Compiler and Linker Errors". Archived from the original on 2008-02-16. Retrieved 2008-02-12.
  4. "Compiler, Linker and Run-Time Errors".
  5. Cunningham, Ward (2010-03-18). "Compiler Bug". WikiWikiWeb. Retrieved 2017-04-14.
  6. జగదేశ్. "Analyzing a JVM Crash". Retrieved 2017-04-15.


This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.