err.ref

是关于PIC单片机（用picc编译器）的一个DEMO

%checksum error in intel hex file *, line *
checksum error in intel hex file *, line *

A checksum error was found at the specified line in the specified
Intel hex file.  The file may have been corrupted.
%circular indirect definition of symbol *
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.
%class * memory space redefined: */*
class * memory space redefined: */*

A class has been defined in two different memory  spaces.  Either
rename  one  of the classes or, if they are the same class, place
them in the same memory space.
%close error (disk space?)
close error (disk space?)

When the compiler closed a temporary file, an error was reported.
The  most  likely  cause  of  this is that there was insufficient
space on disk for the file. Note  that  temporary  files  may  be
created  on a RAM disk, so even if your hard disk has ample space
it is still possible to get this error.
%common symbol psect conflict: *
common symbol psect conflict: *

A common symbol has been defined to be in more than one psect.
%complex relocation not supported for -r or -l options yet
complex relocation not supported for -r or -l options yet

The linker was given a -R or -L option  with  file  that  contain
complex relocation. This is not yet supported.
%conflicting fnconf records
conflicting fnconf records

This is probably caused by  multiple  run-time  startoff  module.
Check the linker arguments, or "Object Files..." in HPD.
%constant conditional branch
constant conditional branch

A conditional branch (generated by an "if" statement etc.) always
follows the same path. This may indicate an expression with miss-
ing or badly placed parentheses, causing the evaluation to  yield
a  value different to what you expected, or it may be because you
have written something like "while(1)". To  produce  an  infinite
loop, use "for(;;)".
%constant conditional branch: possible use of = instead of ==
constant conditional branch: possible use of = instead of ==

There is an expression inside an if  or  other  conditional  con-
struct,  where  a  constant is being assigned to a variable. This
may mean you have inadvertently used an assignment (=) instead of
a compare (==).
%constant expression required
constant expression required

In this context an expression is required that can  be  evaluated
to a constant at compile time.
%constant left operand to ?
constant left operand to ?

The left operand to a conditional operator (?) is constant,  thus
the result of the tertiary operator ?: will always be the same.
%constant operand to || or &&
constant operand to || or &&

One operand to the logical operators ||  or  &&  is  a  constant.
Check the expression for missing or badly placed parentheses.
%constant relational expression
constant relational expression

There is a relational expression that  will  always  be  true  or
false.  This  may  be  because e.g. you are comparing an unsigned
number with a negative value, or  comparing  a  variable  with  a
value greater than the largest number it can represent.
%control line * within macro expansion
control line * within macro expansion

A preprocessor control line (one starting with a #) has been  en-
countered while expanding a macro. This should not happen.
%conversion to shorter data type
conversion to shorter data type

Truncation may occur in this  expression  as  the  lvalue  is  of
shorter type than the rvalue.
%copyexpr: can't handle v_rtype = *
copyexpr: can't handle v_rtype = *

This is an internal assembler error.  Contact  HI-TECH  technical
support with full details of the code that caused this error.
%declaration of * hides outer declaration
declaration of * hides outer declaration

An object has been declared that has the same name  as  an  outer
declaration  (i.e. one outside and preceding the current function
or block). This is legal, but can lead to accidental use  of  one
variable when the outer one was intended.
%declarator too complex
declarator too complex

This declarator is too complex for the compiler to handle.  Exam-
ine  the  declaration  and find a way to simplify it. If the com-
piler finds it too complex, so will anybody maintaining the code.
%default case redefined
default case redefined

There is only allowed to be  one  "default"  label  in  a  switch
statement. You have more than one.
%degenerate signed comparison
degenerate signed comparison

There is a comparision of a signed value with the  most  negative
value  possible for this type, such that the comparision will al-
ways be true or false. E.g.char c;if(c  >=  -128)will  always  be
true,  because  an 8 bit signed char has a maximum negative value
of -128.
%degenerate unsigned comparison
degenerate unsigned comparison

There is a comparision of an unsigned value with zero, which will
always be true or false. E.g.unsigned char c;
if(c >= 0)will always be true, because an unsigned value can nev-
er be less than zero.
%delete what ?
delete what ?

The librarian requires one or more modules to be listed for dele-
tion when using the 'd' key.
%delta= must specify a positive constant
delta= must specify a positive constant

The parameter to the PSECT assembler directive's  'DELTA'  option
must be a positive constant number.
%demo version will only generate * lines of code
demo version will only generate * lines of code

The demonstration version of the compiler is limited in the  size
of  the  code it will generate. The retail version has no limita-
tion on the number of lines of code generated.
%digit out of range
digit out of range

A digit in this number is out of  range  of  the  radix  for  the
number,  e.g. using the digit 8 in an octal number, or hex digits
A-F in a decimal number. An octal number is denoted by the  digit
string  commencing  with  a  zero, while a hex number starts with
"0X" or "0x".
%dimension required
dimension required

Only the most significant (i.e. the first) dimension in a  multi-
dimension  array  may not be assigned a value. All succeeding di-
mensions must be present.
%direct range check failed *
direct range check failed *

The direct addressing was out of range.
%divide by zero in #if, zero result assumed
divide by zero in #if, zero result assumed

Inside a #if expression, there is a division by  zero  which  has
been treated as yielding zero.
%division by zero
division by zero

A constant expression that was being evaluated involved  a  divi-
sion by zero.
%double float argument required
double float argument required

The printf format specifier corresponding to this argument is  %f
or  similar,  and requires a floating point expression. Check for
missing or extra format specifiers or arguments to printf.
%ds argument must be a positive constant
ds argument must be a positive constant

The argument to the DS assembler directive  must  be  a  positive
constant.
%duplicate -d or -h flag
duplicate -d or -h flag

The a symbol file name has been specified to  the  linker  for  a
second time.
%duplicate -m flag
duplicate -m flag

The linker only likes to see one -m flag, unless one of them does
not  specify a file name. Two map file names are more than it can
handle!
%duplicate arch for * in chipinfo file at line *
duplicate arch for * in chipinfo file at line *

The            chipinfo            file            (libicinfo.ini
by  default)  has  a processor section with multiple ARCH values.
Only one ARCH value is allowed.
%duplicate banks for * in chipinfo file at line *
duplicate banks for * in chipinfo file at line *

The            chipinfo            file            (libicinfo.ini
by  default)  has a processor section with multiple BANKS values.
Only one BANKS value is allowed.
%duplicate case label *
duplicate case label *

There is more than one case label with this  value  in  a  switch
statement.
%duplicate label *
duplicate label *

The same name is used for a label more than once  in  this  func-
tion.  Note  that the scope of labels is the entire function, not
just the block that encloses a label.
%duplicate lib for * in chipinfo file at line *
duplicate lib for * in chipinfo file at line *

The            chipinfo            file            (libicinfo.ini
by  default)  has  a  processor section with multiple LIB values.
Only one LIB value is allowed.
%duplicate qualifier
duplicate qualifier

There are two occurrences of the  same  qualifier  in  this  type
specification.  This can occur either directly or through the use
of a typedef. Remove the redundant qualifier.
%duplicate qualifier key *
duplicate qualifier key *

This qualifier key (given via a -Q option) has been used twice.
%duplicate qualifier name *
duplicate qualifier name *

A duplicate qualifier name has been specified to P1 via a -Q  op-
tion.  This should not occur if the standard compiler drivers are
used.
%duplicate romsize for * in chipinfo file at line *
duplicate romsize for * in chipinfo file at line *

The            chipinfo            file            (libicinfo.ini
by default) has a processor section with multiple ROMSIZE values.
Only one ROMSIZE value is allowed.
%duplicate sparebit for * in chipinfo file at line *
duplicate sparebit for * in chipinfo file at line *

The            chipinfo            file            (libicinfo.ini
by  default)  has  a  processor  section  with  multiple SPAREBIT
values. Only one SPAREBIT value is allowed.
%duplicate start for * in chipinfo file at line *
duplicate start for * in chipinfo file at line *

The            chipinfo            file            (libicinfo.ini
by  default)  has a processor section with multiple START values.
Only one START value is allowed.
%duplicate zeroreg for * in chipinfo file at line *
duplicate zeroreg for * in chipinfo file at line *

The            chipinfo            file            (libicinfo.ini
by default) has a processor section with multiple ZEROREG values.
Only one ZEROREG value is allowed.
%empty chip info file *
empty chip info file *

The            chipinfo            file            (libicinfo.ini
by default) contains no data.
%end of file within macro argument from line *
end of file within macro argument from line *

A macro argument has not been terminated. This probably means the
closing parenthesis has been omitted from a macro invocation. The
line number given is the line where the macro argument started.
%end of string in format specifier
end of string in format specifier

The format specifier for the  printf()  style  function  is  mal-
formed.
%entry point multiply defined
entry point multiply defined

There is more than one entry point defined in  the  object  files
given the linker.
%enum tag or { expected
enum tag or { expected

After the keyword "enum" must come either an identifier  that  is
or will be defined as an enum tag, or an opening brace.
%eof in #asm
eof in #asm

An end of file has been encountered inside  a  #asm  block.  This
probably means the #endasm is missing or misspelt.
%eof in comment
eof in comment

End of file was encountered inside a comment. Check for a missing
closing comment flag.
%eof inside conditional
eof inside conditional

END-of-FILE was encountered while  scanning  for  an  "endif"  to
match a previous "if".
%eof inside macro def'n
eof inside macro def'n

End-of-file was encountered while processing a macro  definition.
This means there is a missing "endm" directive.
%eof on string file
eof on string file

P1 has encountered an unexpected end-of-file while re-reading its
file  used  to store constant strings before sorting and merging.
This is most probably due to running out  of  disk  space.  Check
free disk space, OR RAM disk size. The RAM disk may be too small,
if it is used for temporary files.
%error closing output file
error closing output file

The compiler detected an error when closing  a  file.  This  most
probably  means  there  is insufficient disk space, but note that
the file could be on a RAM disk, so even if you have ample  space
on  your  hard  disk,  this error can still occur. If this is the
case, increase the size of your ram disk or move  your  temporary
file area onto the hard disk.
%error dumping *
error dumping *

Either the input file to Cromwell is of an  unsupported  type  or
that file cannot be dumped to the screen.
%error in format string
error in format string

There is an error in the format string here. The string has  been
interpreted as a printf() style format string, and it is not syn-
tactically correct. If not corrected, this will cause  unexpected
behaviour at run time.
%evaluation period has expired
evaluation period has expired

The evaluation period for this compiler has expired. Contact  HI-
TECH to purchase a full licence.
%expand - bad how
expand - bad how

This is an internal code generator error. Contact HI-TECH techni-
cal support with full details of the code that caused this error.
%expand - bad which
expand - bad which

This is an internal code generator error. Contact HI-TECH techni-
cal support with full details of the code that caused this error.
%expected '-' in -a spec
expected '-' in -a spec

There should be a minus sign (-) between the  high  and  low  ad-
dresses in a -A spec, e.g.-AROM=1000h-1FFFh
%exponent expected
exponent expected

A floating point constant must have at least one digit after  the
"e" or "E".
%expression error
expression error

There is a syntax error in this expression, OR there is an  error
in  the  intermediate  code file. This could be caused by running
out of disk (or RAMdisk) space.
%expression generates no code
expression generates no code

This expression generates no code. Check for things like  leaving
off the parentheses in a function call.
%expression stack overflow at op *
expression stack overflow at op *

Expressions in #if lines are evaluated using a stack with a  size
of  128.  It is possible fo