Microchip Technology XC8 Standard Compiler (Workstation) SW006021-1 SW006021-1 ユーザーズマニュアル
製品コード
SW006021-1
MPLAB
®
XC8 C Compiler User’s Guide
DS52053B-page 104
2012 Microchip Technology Inc.
4.8.28
--ERRFORMAT: Define Format for Compiler Messages
If the --ERRFORMAT option is not used, the default behavior of the compiler is to dis-
play any errors in a “human readable” form. This standard format is perfectly accept-
able to a person reading the error output, but is not generally usable with environments
which support compiler error handling.
play any errors in a “human readable” form. This standard format is perfectly accept-
able to a person reading the error output, but is not generally usable with environments
which support compiler error handling.
This option allows the exact format of printed error messages to be specified using spe-
cial placeholders embedded within a message template. See Section 4.6 “Compiler
Messages” for full details of the messaging system employed by xc8, and the
placeholders which can be used with this option.
cial placeholders embedded within a message template. See Section 4.6 “Compiler
Messages” for full details of the messaging system employed by xc8, and the
placeholders which can be used with this option.
This section is also applicable to the --WARNFORMAT and --MSGFORMAT options,
which adjust the format of warning and advisory messages, respectively.
which adjust the format of warning and advisory messages, respectively.
If you are compiling using MPLAB IDE, the format of the compiler messages is auto-
matically configured to what the IDE expects. It recommended that you do not adjust
the message formats if compiling using this IDE.
matically configured to what the IDE expects. It recommended that you do not adjust
the message formats if compiling using this IDE.
4.8.29
--ERRORS: Maximum Number of Errors
This option sets the maximum number of errors each compiler application, as well as
the driver, will display before execution is terminated. By default, up to 20 error
messages will be displayed by each application.
the driver, will display before execution is terminated. By default, up to 20 error
messages will be displayed by each application.
See Section 4.6 “Compiler Messages” for full details of the messaging system
employed by xc8.
employed by xc8.
4.8.30
--FILL: Fill Unused Program Memory
This option allows specification of a hexadecimal opcode that can be used to fill all
unused program memory locations. This option utilizes the features of the HEXMATE
application, so it is only available when producing a HEX output file, which is the default
operation.
unused program memory locations. This option utilizes the features of the HEXMATE
application, so it is only available when producing a HEX output file, which is the default
operation.
This driver feature allows you to compile and fill unused locations in one step. If you
prefer not to use the driver option and prefer to fill unused locations after compilation,
then you will need to explicitly use the HEXMATE application. Note the corresponding
option in HEXMATE is -FILL (one leading dash) as opposed to the drivers --FILL
option. Note, also, that the unused tag which can be specified with the driver option
does not exist in the HEXMATE options.
prefer not to use the driver option and prefer to fill unused locations after compilation,
then you will need to explicitly use the HEXMATE application. Note the corresponding
option in HEXMATE is -FILL (one leading dash) as opposed to the drivers --FILL
option. Note, also, that the unused tag which can be specified with the driver option
does not exist in the HEXMATE options.
The usage of the driver option is:
--FILL=[const_width:]fill_expr[@address[:end_address]]
where:
• const_width has the form wn and signifies the width (n bytes) of each constant
in fill_expr. If const_width is not specified, the default value is the native
width of the architecture. That is, --
width of the architecture. That is, --
FILL
=w1:1
with fill every byte with the value
0x01.
• fill_expr can use the syntax (where const and increment are n-byte
constants):
- const fill memory with a repeating constant; i.e., --
FILL
=0xBEEF
becomes
0xBEEF, 0xBEEF, 0xBEEF, 0xBEEF
- const+=increment fill memory with an incrementing constant; i.e.,
--fill=0xBEEF+=1
becomes 0xBEEF, 0xBEF0, 0xBEF1, 0xBEF2
- const-=increment fill memory with a decrementing constant; i.e.,
--fill=0xBEEF-=0x10
becomes 0xBEEF, 0xBEDF, 0xBECF, 0xBEBF
- const,const,...,const fill memory with a list of repeating constants; i.e.,
--
FILL
=0xDEAD,0xBEEF
becomes 0xDEAD,0xBEEF,0xDEAD,0xBEEF