11.07.2015 Views

PicC 9.50 dsPIC Manual.pdf

PicC 9.50 dsPIC Manual.pdf

PicC 9.50 dsPIC Manual.pdf

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Linker and UtilitiesMap Filestext 72 72 82hello.obj text F4 F4 7C:\HT-Z80\LIB\z80-sc.libpowerup.obj vectors 71 71 1TOTAL Name Link Load LengthCLASS CODEvectors 0 0 72const FB FB 1CLASStext 72 72 89DATAbss 8000 8000 24SEGMENTS Name Load Length Top Selectorvectors 000000 0000FC 0000FC 0bss 008000 000024 008024 80005.9.1 Call Graph InformationA call graph is produced for chip types and memory models that use a compiled stack, rather than ahardware stack, to facilitate parameter passing between functions and auto variables defined withina function. When a compiled stack is used, functions are not re-entrant since the function will use afixed area of memory for its local objects (parameters/auto variables). A function called foo(), forexample, will use symbols like ?_foo for parameters and ?a_foo for auto variables. Compilers suchas the PIC, 6805 and V8 use compiled stacks. The 8051 compiler uses a compiled stack in small andmedium memory models. The call graph shows information relating to the placement of functionparameters and auto variables by the linker. A typical call graph may look something like:Call graph:*_main size 0,0 offset 0_init size 2,3 offset 0_ports size 2,2 offset 5* _sprintf size 5,10 offset 0* _putchINDIRECT 4194INDIRECT 4194_function_2 size 2,2 offset 0_function size 2,2 offset 5*_isr->_incr size 2,0 offset 15The graph shows the functions called and the memory usage (RAM) of the functions for their ownlocal objects. In the example above, the symbol _main is associated with the function main(). It is101

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!