Atmel CAVR-4 사용자 설명서

CAVR-4

Part 2. Compiler reference

This chapter describes the format of the diagnostic messages and explains how 

diagnostic messages are divided into different levels of severity. 

All diagnostic messages are issued as complete, self-explanatory messages. A typical 
diagnostic message from the compiler is produced in the form:

filename,linenumber level[tag]: message

where 

 is the name of the source file in which the error was encountered, 

 is the line number at which the compiler detected the error, 

 is the 

level of seriousness of the diagnostic, 

 is a unique tag that identifies the diagnostic 

message, and 

 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.

Use the option 

--diagnostics_tables

 to list all possible compiler diagnostic 

messages in a named file.

The diagnostics are divided into different levels of severity:

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.

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 

--no_warnings

, see