Microchip Technology XC8 Standard Compiler (Workstation) SW006021-1 SW006021-1 ユーザーズマニュアル
製品コード
SW006021-1
MPLAB
®
XC8 C Compiler User’s Guide
DS52053B-page 462
2012 Microchip Technology Inc.
(1247) no access RAM defined for variable placement
(Code Generator)
No memory has been specified to cover the access bank memory.
(1248) symbol (*) encountered with undefined type size
(Code Generator)
The code generator was asked to position a variable, but the size of the variable is not
known. This is an internal compiler error. Contact Microchip Technical Support with
details.
known. This is an internal compiler error. Contact Microchip Technical Support with
details.
MESSAGES 1250-1499
(1250) could not find space (* byte*) for variable *
(Code Generator)
The code generator could not find space in the banked RAM for the variable specified.
(1253) could not find space (* byte*) for auto/param block
(Code Generator)
The code generator could not find space in RAM for the psect that holds auto and
parameter variables.
parameter variables.
(1254) could not find space (* byte*) for data block
(Code Generator)
The code generator could not find space in RAM for the data psect that holds initialized
variables.
variables.
(1255) conflicting paths for output directory
(Driver)
The compiler has been given contradictory paths for the output directory via any of the
-O
-O
or --OUTDIR options, for example:
--outdir=../../ -o../main.HEX
(1256) undefined symbol "*" treated as HEX constant
(Assembler)
A token which could either be interpreted as a symbol or a hexadecimal value does not
match any previously defined symbol and so will be interpreted as the latter. Use a
leading zero to avoid the ambiguity, or use an alternate radix specifier such as 0x. For
example:
match any previously defined symbol and so will be interpreted as the latter. Use a
leading zero to avoid the ambiguity, or use an alternate radix specifier such as 0x. For
example:
MOV a, F7h ; is this the symbol F7h, or the HEX number 0xF7?
(1257) local variable "*" is used but never given a value
(Code Generator)
An auto variable has been defined and used in an expression, but it has not been
assigned a value in the C code before its first use. Auto variables are not cleared on
startup and their initial value is undefined. For example:
assigned a value in the C code before its first use. Auto variables are not cleared on
startup and their initial value is undefined. For example:
void main(void) {
double src, out;
out = sin(src); /* oops -- what value was in src? */
(1258) possible stack overflow when calling function "*"
(Code Generator)
The call tree analysis by the code generator indicates that the hardware stack may
overflow. This should be treated as a guide only. Interrupts, the assembler optimizer
and the program structure may affect the stack usage. The stack usage is based on the
C program and does not include any call tree derived from assembly code.
overflow. This should be treated as a guide only. Interrupts, the assembler optimizer
and the program structure may affect the stack usage. The stack usage is based on the
C program and does not include any call tree derived from assembly code.
(1259) can’t optimize for both speed and space
(Driver)
The driver has been given contradictory options of compile for speed and compile for
space, for example:
space, for example:
--opt=speed,space