PicC 9.50 dsPIC Manual.pdf

DSPICC Compiler OptionsDSPICC Command-line DriverTable 2.7: Runtime environment suboptionsSuboption Controls On (+) impliesinit The code present in the startup modulethat copies the data psect’s ROM-image toThe data psect’s ROM image iscopied into RAM.RAM.clib The inclusion of library files into the outputcode by the linker.Library files are linked into theoutput.clear The code present in the startup module that The bss psect is cleared.clears the bss psects.stack The code present in the startup module that The stack pointer is initialized.initializes the stack pointer.keep Whether the startup module source file is The startup module is not deleted.deleted after compilation.no_startup Whether a startup module is produced andlinked into the output.The startup module is not generatedor linked into the output.vec_init Initialization of unused interrupt vectors. Unused interrupt vectors will beset to the reset vector.for example. To only use an external range and ignore any on-chip memory, use:--ROM=1000-2fffThis option may also be used to reserve memory ranges already defined as on-chip memory in thechipinfo file. To do this supply a range prefixed with a minus character, -, for example:--ROM=default,-1000-1fffwill use all the defined on-chip memory, but not use the addresses in the range from 1000h to 1fffhfor allocation of ROM objects.2.4.41 --RUNTIME=type: Specify Runtime EnvironmentThe --RUNTIME option is used to control what is included as part of the runtime environment. Theruntime environment encapsulates any code that is present at runtime which has not been defined bythe user, instead supplied by the compiler, typically as library code.All runtime features are enabled by default and this option is not required for normal compilation.The usable suboptions include those shown in Table 2.7.20