SW500010 Microchip Technology, SW500010 Datasheet - Page 28

• 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

Runtime Files
2.2.3.1 Printf check
An extra execution of the code generator is performed for prior to the actual code generation phase.
This pass is part of the process by which the printf library function is customized, see Section
for more details.
2.2.3.2 Assembly Code Requirements
After pre-processing and parsing of any C source files, but before code generation of these files, the
compiler assembles any assembly source files to relocatable object files. These object files, together
with any object files specified on the command line, are scanned by the compiler driver and certain
information from these files are collated and passed to the code generator. Several actions are taken
based on this information. See Section 3.10.4.
are used, but not defined, in the assembly/object code. This allows variables to be defined in C
code, and only every referenced in assembly code. Normally such C variables would be removed
as the code generator would consider them to be used (from the C perspective). Specifically, the
C variables are automatically qualified as being volatile which is sufficient to prevent the code
generator making this optimization.
flags) in the assembly/object code. The memory occupied by the psects is removed from the available
memory ranges passes to the code generator and linker. This information ensures that this memory
is not allocated to any C resources.
2.3 Runtime Files
In addition to the input files specified on the command line by the user, there are also compiler-
generated source files and pre-compiled library files which might be compiled into the project by the
driver. These are:
Strictly speaking the powerup routine is neither compiler-generated source, nor a library routine. It
is fully defined by the user, however as it is very closely associated with the runtime startup module,
it is discussed with the other runtime files in the following sections.
28
The driver instructs the code generator to preserve any C variables which map to symbols which
The driver also takes note of any absolute psects (viz. use the abs and ovrld PSECT directive
Library files;
The runtime startup module;
The powerup routine; and
The printf routine.
PICC Command-line Driver
2.3.4