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

Descriptions of implementation-defined behaviorAllocation order of bitfields within a unit (6.5.2.1)Bitfields are allocated within an integer from least-significant to most-significant bit.Can bitfields straddle a storage-unit boundary (6.5.2.1)Bitfields cannot straddle a storage-unit boundary for the chosen bitfield integer type.Integer type chosen to represent enumeration types (6.5.2.2)The chosen integer type for a specific enumeration type depends on the enumerationconstants defined for the enumeration type. The chosen integer type is the smallestpossible.QUALIFIERSAccess to volatile objects (6.5.3)Any reference to an object with volatile qualified type is an access.DECLARATORSMaximum numbers of declarators (6.5.4)The number of declarators is not limited. The number is limited only by the availablememory.STATEMENTSMaximum number of case statements (6.6.4.2)The number of case statements (case values) in a switch statement is not limited. Thenumber is limited only by the available memory.PREPROCESSING DIRECTIVESCharacter constants and conditional inclusion (6.8.1)The character set used in the preprocessor directives is the same as the executioncharacter set. The preprocessor recognizes negative character values if a 'plain' characteris treated as a signed character.Including bracketed filenames (6.8.2)For file specifications enclosed in angle brackets, the preprocessor does not searchdirectories of the parent files. A parent file is the file that contains the #include256MSP430 IAR C/C++ CompilerReference Guide