SW500010 Microchip Technology, SW500010 Datasheet - Page 406

• 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

which masks out the top bits of the address containing the bank information.
bler list file look back up the file from the instruction at fault to determine which C statement has
generated this instruction. You will then need to examine the C code for possible errors. incorrectly
qualified pointers are an common trigger.
(478) * range check failed (location 0x* (0x*+*), value 0x* > limit 0x*)
This is an internal compiler error. Contact HI-TECH Software technical support with details.
(479) circular indirect definition of symbol "*"
The specified symbol has been equated to an external symbol which, in turn, has been equated to the
first symbol.
(480) function signatures do not match: * (*): 0x*/0x*
The specified function has different signatures in different modules. This means it has been declared
differently, e.g. it may have been prototyped in one module and not another. Check what declarations
for the function are visible in the two modules specified and make sure they are compatible, e.g.:
(481) common symbol "*" psect conflict
A common symbol has been defined to be in more than one psect.
(482) symbol "*" is defined more than once in "*"
This symbol has been defined in more than one place. The assembler will issue this error if a symbol
is defined more than once in the same module, e.g.:
406
If the assembler instruction that caused this error was generated by the compiler, in the assem-
extern int get_value(int in);
/ * and in another module: * /
/ * this is different to the declaration * /
int get_value(int in, char type)
{
_next:
_next:
move r0, #55
move [r1], r0
; oops -- choose a different name
Error and Warning Messages
(Assembler)
(Linker)
(Linker)
(Linker)
(Linker)