SW500010 Microchip Technology, SW500010 Datasheet - Page 159

• Manufacturer Part Number: SW500010
• Description: HI-TECH C PRO FOR PIC10/12/16
• Manufacturer: Microchip Technology
• Type: Compilerr
• Series: PIC10/12/16r

Specifications of SW500010

• Supported Families: PIC10, PIC12, PIC16
• Core Architecture: PIC
• Software Edition: Professional
• Kit Contents: Software And Docs
• Mcu Supported Families: PIC10/12/16
• Tool Type: Compiler
• Lead Free Status / RoHS Status: Not applicable / Not applicable
• For Use With/related Products: PIC10, PIC12, PIC14, PIC16, PIC16E
• Lead Free Status / Rohs Status: Lead free / RoHS Compliant
• Other names: 019P; 778-1006; 778-1006

Linker and Utilities
5.10.2.2 Call Graph Information
A call graph is produced and displayed in the map file for target devices and memory models that
use a compiled stack to facilitate parameter passing between functions and auto variables. See
Section
which is primarily used to allow overlapping of functions’ APBs. The following information can be
obtained from studying the call graph:
The call graph in the map file shows the information collated and interpreted by the linker,
First the program is compiled without using this option and the following linker class
definition is noted in the linker command line:
-ACODE=0-03FFFhx2
The class name may vary between compilers and the selected target device, however
there is typically a class that is defined to cover the entire memory space used by the
device.
The driver option --ROM=default,-4000-400F is then used and the map file re-
sulting from the subsequent build shows the following change:
-ACODE=0-03FFFh,04010h-07FFFh
which confirms that the memory option was seen by the linker and that the memory
requested was reserved.
The functions in the program that are “root” nodes marking the top of a call tree, and which
are not directly called;
The functions that the linker deemed were called, or may have been called, during program
execution;
The program’s hierarchy of function calls;
The size of the auto and parameter areas within each function’s APB;
The offset of each function’s APB within the program’s auto/parameter psect;
Which functions’ APBs are consuming memory not overlapped by the APB of any other
function (on the critical path);
Which functions are called indirectly;
Which functions are called as part of a parameter expression for another function; and
5.9
for more detailed information on compiled stack operation.
Map Files
159