Diagnostic messages provide syntactic and semantic information about your source text. Syntactic information can include, for example, syntax errors and use of non-ANSI Fortran. Semantic information includes, for example, unreachable code.
Diagnostic messages can be any of the following: command-line diagnostics, warning messages, error messages, or catastrophic error messages.
These messages report improper command-line options or arguments. If the command line contains an unrecognized option, the compiler passes the option to the linker. If the linker still does not recognize the option, the linker produces the diagnostic message.
Command-line error messages appear on the standard error device in the form:
driver-name: message
where
|
driver-name |
The name of the compiler driver. |
|
message |
Describes the error. |
Command-line warning messages appear as follows:
driver-name: warning: message
These messages describe diagnostics that are reported during the processing of the source file. These diagnostics have the following format:
filename(linenum): type nn: message
|
filename |
Indicates the name of the source file currently being processed. An extension to the filename indicates the type of the source file, as follows: .f, f90, .for indicate a Fortran file. |
|
linenum |
Indicates the source line where the compiler detects the condition. |
|
type |
Indicates the severity of the diagnostic message: warning, error, or Fatal error. |
|
nn |
The number assigned to the error (or warning) message. |
|
message |
Describes the diagnostic. |
The following is an example of a warning message:
tantst.f(3): warning 328:"local variable": Local variable "increment" never used.
The compiler can also display internal error messages on the standard error device. If your compilation produces any internal errors, contact your Intel representative. Internal error messages are in the form:
FATAL COMPILER ERROR: message