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

Diagnostics●●●Diagnostic messagesDiagnostic messages are directed to stderr and displayed on the screen, as well asprinted in an optional list file. To read more about diagnostic messages, seeDiagnostics, page 136.Error return codesThese codes provide status information to the operating system which can be testedin a batch file, see Error return codes, page 136.Size informationInformation about the generated amount of bytes for functions and data for eachmemory is directed to stdout and displayed on the screen. Some of the bytes mightbe reported as shared.Shared objects are functions or data objects that are shared between modules. If anyof these occur in more than one module, only one copy will be retained. For example,in some cases inline functions are not inlined, which means that they are marked asshared, because only one instance of each function will be included in the finalapplication. This mechanism is sometimes also used for compiler-generated code ordata not directly associated with a particular function or variable, and when only oneinstance is required in the final application.Error return codesThe MSP430 IAR C/C++ Compiler returns status information to the operating systemthat can be tested in a batch file.The following command line error codes are supported:CodeDescription0 Compilation successful, but there may have been warnings.1 There were warnings and the option --warnings_affect_exit_code wasused.2 There were errors.3 There were fatal errors making the compiler abort.4 There were internal errors making the compiler abort.Table 28: Error return codesDiagnosticsThis section describes the format of the diagnostic messages and explains howdiagnostic messages are divided into different levels of severity.136MSP430 IAR C/C++ CompilerReference Guide