Understanding And Handling Compiler Errors - Texas Instruments TMS320C2x User Manual

Understanding and Handling Compiler Errors

2.8 Understanding and Handling Compiler Errors
2-36
One of the compiler's primary functions is to detect and report errors in the
source program. When the compiler encounters an error in your program, it
displays a message in the following format:
"file.c", line n: [ECODE] error message
"file.c" identifies the filename.
line n identifies the line number where the error occurs.
ECODE is a 4-character error code. A single upper-case letter
identifies the error class; a 3-digit number uniquely
identifies the error.
error message is the text of the message.
Errors in C code are divided into classes according to severity; these classes
are identified by the letters W, E, F, and I (upper-case i). The compiler also
reports other errors that are not related to C but prevent compilation. Exam-
ples of each level of error message are located in Table 2−3.
Code-W errors are warnings resulting from a condition that is technically
-
undefined according to the rules of the language or that can cause unex-
pected results. The compiler continues running when this occurs.
Code-E errors are recoverable, resulting from a condition that violates
-
the semantic rules of the language. Although these are normally fatal
errors, the compiler can recover and generate an output file if you use
the −pe option. See to section 2.8.2, Treating Code-E Errors as Warnings
(−pe Option), on page 2-37 for more information.
Code-F errors are fatal, resulting from a condition that violates the syn-
-
tactic or semantic rules of the language. The compiler cannot recover and
does not generate output for code-F errors.
Code-I errors are implementation errors, occurring when one of the
-
compiler's internal limits is exceeded. These errors are usually caused by
extreme behavior in the source code rather than by explicit errors. In most
cases, code-I errors cause the compiler to abort immediately. Most
code-I messages contain the maximum value for the limit that was
exceeded. (Those limits that are absolute are also listed in section 5.9,
Compiler Limits, on page 5-16.)
Other error messages, such as incorrect command line syntax or
-
inability to find specified files, are usually fatal. They are identified by the
symbol >> preceding the message.