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

C++ dynamic initializationINTERRUPT VECTORSThe interrupt vector table contains pointers to interrupt routines, including the resetroutine. The table is placed in the segment INTVEC. For the MSP430 microcontroller, itshould end at address 0xFFFF. For a device with 16 interrupt vectors, this means that thesegment should start at the address 0xFFE0, for example:-Z(CONST)INTVEC=FFE0-FFFFThe system startup code places the reset vector in the RESET segment; the INTVECsegment cannot be used by the system startup code because the size of the interruptvector table varies between different devices. In the linker command file it can look likethis:-Z(CONST)RESET=FFFE-FFFFAn application that does not use the standard startup code can either use the RESETsegment, or define an interrupt function on the reset vector, in which case the INTVECsegment is used.C++ dynamic initializationIn C++, all global objects will be created before the main function is called. The creationof objects can involve the execution of a constructor.The DIFUNCT segment contains a vector of addresses that point to initialization code.All entries in the vector will be called when the system is initialized.For example:-Z(CONST)DIFUNCT=1100-FFFEFor additional information, see DIFUNCT, page 248.Verifying the linked result of code and data placementThe linker has several features that help you to manage code and data placement, forexample, messages at link time and the linker map file.SEGMENT TOO LONG ERRORS AND RANGE ERRORSAll code or data that is placed in relocatable segments will have its absolute addressesresolved at link time. It is also at link time it is known whether all segments will fit inthe reserved memory ranges. If the contents of a segment do not fit in the address rangedefined in the linker command file, XLINK will issue a segment too long error.42MSP430 IAR C/C++ CompilerReference Guide