SW500010 Microchip Technology, SW500010 Datasheet - Page 166

• 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

Map Files
The list of files, that make up the program, indicated in this section of the map file will typically
consist of one or more object files derived from input source code. The map file produced by PRO
compilers will show one object file derived from all C source modules, however Standard version
compilers will show one object file per C source module.
precompiled into an object file, in the case of Standard version compilers, or is a compiler-written
assembler source file, which is then compiled along with the remainder of the program. In either
case, an object file module will be listed in this section, along with those psects which it defines.
If the startup module is not being deleted after compilation (see the --RUNTIME option in Section
2.6.50) then the module name will be startup.obj, otherwise this module will have a system-
dependent temporary file name, stored in a system-dependent location.
printed as a header, followed by a list of the modules that contributed to the output. Only mod-
ules that define symbols that are referenced are included in the program output. For example, the
following:
indicates that both the i1aldiv.obj and aldiv.obj modules were linked in from the library
file pic86l-c.lib.
tribution to the program from program-wide psects, in particular that used by the compiled stack
auto/parameter area.
166
In addition, there will typically be the runtime startup module. The runtime startup code is
Modules derived from library files area also shown in this list. The name of the library file is
Underneath the library file contributions, there may be a label COMMON. This shows the con-
This indicates that one of the files that the linker processed was called ext.obj. (This
may have been derived from ext.c or ext.as.) This object file contained a text
psect, as well as psects called bss and rbit. The psect text was linked at address
3A and bss at address 4B. At first glance, this seems to be a problem given that text
is 22 words long, however note that they are in different memory areas, as indicated by
the Space flag (0 for text and 1 for bss), and so do not occupy the same memory.
The psect rbit contains bit objects, as indicated by its Scale value (its name is a bit of
a giveaway too). Again, at first glance there seems there could be an issue with rbit
linked over the top of bss. Their Space flags are the same, but since rbit contains bit
objects, all the addresses shown are bit addresses, as indicated by the Scale value of 8.
Note that the Load address field of rbit psect displays the Link address converted to
byte units, i.e. 50h/8 => Ah.
C:\program files\HI-TECH Software\PICC-18\9.50\lib\pic86l-c.lib
i1aldiv.obj
aldiv.obj
text 174 174
text
90
90
3C
3C
C
C
0
0
Linker and Utilities