MSP430 IAR C/C++ Compiler reference guide - Rice University

External interface detailsMESSAGE FORMATAll diagnostic messages are issued as complete, self-explanatory messages. A typicaldiagnostic message from the compiler is produced in the form:filename,linenumber level[tag]: messagewith the following elements:filenamelinenumberleveltagmessageThe name of the source file in which the issue was encounteredThe line number at which the compiler detected the issueThe level of seriousness of the issueA unique tag that identifies the diagnostic messageAn explanation, possibly several lines longDiagnostic messages are displayed on the screen, as well as printed in the optional listfile.Use the option --diagnostics_tables to list all possible compiler diagnosticmessages.SEVERITY LEVELSThe diagnostic messages are divided into different levels of severity:RemarkA diagnostic message that is produced when the compiler finds a source codeconstruction that can possibly lead to erroneous behavior in the generated code.Remarks are by default not issued, but can be enabled, see --remarks, page 164.WarningA diagnostic message that is produced when the compiler finds a programming error oromission which is of concern, but not so severe as to prevent the completion ofcompilation. Warnings can be disabled by use of the command line option--no_warnings, see page 159.ErrorA diagnostic message that is produced when the compiler has found a constructionwhich clearly violates the C or C++ language rules, such that code cannot be produced.An error will produce a non-zero exit code.Part 2. Compiler reference137