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

Checking module consistencyObject file Color Tastefile2 red not definedfile3 red *file4 red spicyfile5 red leanTable 20: Example of runtime model attributes (Continued)USING RUNTIME MODEL ATTRIBUTESRuntime model attributes can be specified in your C/C++ source code to ensure moduleconsistency with other object files by using the #pragma rtmodel directive. Forexample:#pragma rtmodel="__rt_version", "1"For detailed syntax information, see rtmodel, page 212.Runtime model attributes can also be specified in your assembler source code by usingthe RTMODEL assembler directive. For example:RTMODEL "color", "red"For detailed syntax information, see the MSP430 IAR Assembler Reference Guide.Note: The predefined runtime attributes all start with two underscores. Any attributenames you specify yourself should not contain two initial underscores in the name, toeliminate any risk that they will conflict with future IAR runtime attribute names.At link time, the IAR XLINK Linker checks module consistency by ensuring thatmodules with conflicting runtime attributes will not be used together. If conflicts aredetected, an error is issued.PREDEFINED RUNTIME ATTRIBUTESThe table below shows the predefined runtime model attributes that are available for theMSP430 IAR C/C++ Compiler. These can be included in assembler code or in mixedC/C++ and assembler code.Runtime model attribute Value Description__core 430 or 430X Corresponds to the --core option.__data_model small,medium,or largeCorresponds to the data model used in theproject; only available for MSP430X.__double_size 32 or 64 The size, in bits, of the doublefloating-point type.Table 21: Predefined runtime model attributes72MSP430 IAR C/C++ CompilerReference Guide