Atmel CAVR-4 Manuale Utente
CAVR-4
Part 2. Compiler reference
279
Diagnostics
This chapter describes the format of the diagnostic messages and explains how
diagnostic messages are divided into different levels of severity.
Message format
All diagnostic messages are issued as complete, self-explanatory messages. A typical
diagnostic message from the compiler is produced in the form:
diagnostic message from the compiler is produced in the form:
filename,linenumber level[tag]: message
where
filename
is the name of the source file in which the error was encountered,
linenumber
is the line number at which the compiler detected the error,
level
is the
level of seriousness of the diagnostic,
tag
is a unique tag that identifies the diagnostic
message, and
message
is a self-explanatory message, possibly several lines long.
Diagnostic messages are displayed on the screen, as well as printed in the optional list
file.
file.
Use the option
--diagnostics_tables
to list all possible compiler diagnostic
messages in a named file.
Severity levels
The diagnostics are divided into different levels of severity:
Remark
A diagnostic message that is produced when the compiler finds a source code construct
that can possibly lead to erroneous behavior in the generated code. Remarks are by
default not issued, but can be enabled, see --remarks, page 194.
that can possibly lead to erroneous behavior in the generated code. Remarks are by
default not issued, but can be enabled, see --remarks, page 194.
Warning
A diagnostic that is produced when the compiler finds a programming error or omission
which is of concern, but not so severe as to prevent the completion of compilation.
Warnings can be disabled by use of the command-line option
which is of concern, but not so severe as to prevent the completion of compilation.
Warnings can be disabled by use of the command-line option
--no_warnings
, see