"path" specified by the "character string" option is a file. Specify a folder. |
||
The folder "folder" specified by the "character string" option is not found. |
||
The "character string2" option is ignored when the "character string1" option is specified at the same time. |
||
The "-Xfloat" option is ignored because specified device does not have FPU. |
||
"symbol name" specified in the "character string" option is not allowed for a preprocessor macro. |
||
The "character string" option is specified more than once. The latter is valid. |
||
The "character string2" option is ignored when the "character string1" option and the "character string2" option are inconsistent. |
||
The "character string2" option is ignored when the "character string1" option is not specified. |
||
Optimization itemoptions were cleared when "-Ocharacter string" option is specified. Optimization itemoptions need to specify after "-Ocharacter string" option. |
||
[CC-RH] The same file name was specified more than once in a command line. CC-RH is not capable of handling multiple instances of the same file name. |
||
The evaluation version is valid for the remaining number days. |
||
The license manager is not installed. Install the correct license manager. |
||
Type qualifiers are meaningless in this declaration. Ignored. |
||
Too many characters in character constant. Character constants cannot contain more than one character. |
||
Since there is a preceding #else, this directive is illegal. |
||
Shift count is negative. The behavior will be undefined in ANSI-C. |
||
Storage class is not first. Specify the declaration of the storage class first. |
||
A value of type "type1" cannot be used to initialize an entity of type "type2". |
||
Declaration is incompatible with "declaration" (declared at line number). |
||
Argument of type "type1" is incompatible with parameter of type "type2". |
||
External/internal linkage conflict with previous declaration. |
||
Floating-point value does not fit in required integral type. |
||
Argument is incompatible with corresponding format string conversion. |
||
Declaring a void parameter list with a typedef is nonstandard. |
||
Pointless comparison of unsigned integer with a negative constant. |
||
Transfer of control bypasses initialization of: type "symbol" (declared at line number). |
||
Using out-of-scope declaration of type "symbol" (declared at line number). |
||
Subtraction of pointer types "type name1" and "type name2" is nonstandard. |
||
White space between backslash and newline in line splice ignored. |
||
Multicharacter character literal (potential portability problem). |
||
Definition at end of file not followed by a semicolon or a declarator. |
||
The declaration at the end of the file lacked a semicolon to indicate its termination. |
||
White space is required between the macro name "macro name" and its replacement text |
||
Insert a space between the macro name and the text to be replaced. |
||
Using "function item" function at influence the code generation of "SuperH" compiler |
||
The use of "function item" may affect compatibility with the SuperH compiler. Confirm details of differences in the specification. |
||
The same identifier was declared several times and different sections were specified for individual declarations. Only the first section declaration is valid. |
||
argument is incompatible with formal parameter of intrinsic function |
||
const qualifier for variable "variable-name" differs between files. |
||
Illegal operand (range error in immediate). Only the effective lower-order digits will be recognized as being specified, and the assembly will continue. |
||
Only the effective lower-order digits will be recognized as being specified, and the assembly will continue. |
||
Only the effective lower-order digits will be recognized as being specified, and the assembly will continue. |
||
Illegal register number, ignored. The invalid register will be ignored, and the assembly will continue. |
||
string already specified, ignored. The previously specified number will be used. This specification will be ignored. |
||
Illegal register number, aligned odd register(rXX) to be even register(rYY). |
||
Odd-numbered registers (r1, r3, ... r31) have been specified. The only general-purpose registered that can be specified are even-numbered (r0, r2, r4, ... r30). Assembly will continue, assuming that even-numbered registers (r0, r2, r4, ... r30) have been specified. |
||
Duplicated reg_mode, ignored $REG_MODE. The "-Xreg_mode" option takes precedence, and register modes specified via the $REG_MODE control instruction will be ignored. |
||
"path-name" specified by the "character string" option is a file. Specify a folder. |
||
The folder "folder-name" specified by the "character string" option is not found. |
||
"character string2" specified in the "character string1" option is not available. |
||
The "character string" option is specifiedmore than once. The latter is valid. |
||
The "character string2" option is ignored when the "character string1" option and the "character string2" option are inconsistent. |
||
option1 and option2 cannot be specified simultaneously. option1 is ignored. |
||
option and the option to divide the output file cannot be specified simultaneously. option is ignored. The first input file name is used as the output file name. |
||
Fatal level message cannot be changed to other level : "number" |
||
The level of an fatal error message cannot be changed. The specification of number is ignored. Only errors at the information/warning/error level can be changed with the change_message option. |
||
Subcommand file terminated with end option instead of exit option |
||
There is no processing specification following the end option. Processing is done with the exit option assumed. |
||
Duplicate specifications of option were found. Only the last specification is effective. |
||
option was used to specify the same file twice. The second specification is ignored. |
||
option was used to specify the same module twice. The second specification is ignored. |
||
Duplicate symbol/section specified in option "option" : "name" |
||
option was used to specify the same symbol name or section name twice. The second specification is ignored. |
||
option was used to specify the same error number. Only the last specification is effective. |
||
The license manager is not installed. Install the correct license manager. |
||
The symbol name or section name specified in option cannot be found. name specification is ignored. |
||
"name" in rename option conflicts between symbol and section |
||
name specified by the rename option exists as both a section name and as a symbol name. |
||
The symbol specified by option has already been defined. Processing is continued without any change. |
||
Invalid address value specified in option "option" : "address" |
||
address specified by option is invalid. address specification is ignored. |
||
The "-output" option does not accept specification of a section that has no initial value. |
||
A symbol other than symbol specified by the entry option is specified as the entry symbol on compiling or assembling. The option specification is given priority. |
||
section has no addresses specified for it. section will be located at the rearmost address. |
||
Specify the address of the section using the rlink option "-start". |
||
Address cannot be assigned to absolute section "section" in start option |
||
section is an absolute address section. An address assigned to an absolute address section is ignored. |
||
Section address in start option is incompatible with alignment : "section" |
||
The address of section specified by the start option conflicts with memory boundary alignment requirements. The section address is modified to conform to boundary alignment. |
||
Section attribute mismatch in rom option : "section1,section2" |
||
The attributes and boundary alignment of section1 and section2 specified by the rom option are different. The larger value is effective as the boundary alignment of section2. |
||
Load address overflowed out of record-type in option "option" |
||
A record type smaller than the address value was specified. The range exceeding the specified record type has been output as different record type. |
||
Cannot fill unused area from "address" with the specified value |
||
Specified data cannot be output to addresses higher than address because the unused area size is not a multiple of the value specified by the space option. |
||
The section specified in option does not have an externally defined symbol. |
||
Directive command "control directive" is duplicated in "file" |
||
control directive is written in multiple source files. The control directive cannot be written more than once across files. |
||
Failed to write type of output code to the output file. The output file may not contain the address to which type of output code should be output. |
||
The input file contains vector table section. The optimizing linker does not create section automatically. |
||
Interrupt number "vector number" of "section" is defined in input file |
||
The vector number specified by the VECTN option is defined in the input file. Processing is continued with priority given on the definition in the input file. |
||
Section "section" was moved other area specified in option "cpu=<attribute>" |
||
The object size was modified through optimization of access to external variables. Accordingly, section in the area specified by the next cpu specification was moved. |
||
Area of "FIX" is within the range of the area specified by "cpu=<attribute>" :"<start>-<end>" |
||
In the cpu option, the address range of <start>-<end> specified for FIX overlapped with that specified for another memory type. The setting for FIX is valid. |
||
section name, which is a data section without an initial value, cannot be initialized by the initial setup program. |
||
Check the address range specified with -cpu and the sizes of pointer variables. |
||
Section "section name" specified in option "option" is ignored |
||
option specified for the section newly created due to -cpu=stride is invalid. |
||
Section "section" in relocation "file"-"section"-"offset" is changed |
||
The relocation section file offset now refers to a location in the new section created with the division of section. |
||
To prevent division, declare the contiguous_section option for section. |
||
Input file file1 was overwritten. A backup copy of the data in the previous version of file1 was saved in file2. |
||
There is no debugging information in the input files. The "option" has been ignored. |
||
Check whether the relevant option was specified at compilation or assembly. |
||
No inter-module optimization information is present in the input files. The optimize option has been ignored. |
||
Check whether the goptimize option was specified at compilation or assembly. |
||
No stack information is present in the input files. The stack option is ignored. If all input files are assembler output files, the stack option is ignored. |
||
An unsupported section was present in file. section has been ignored. |
||
Debugging information in file is not dwarf2. The debugging information has been deleted. |
||
The symbol named symbol is duplicated. The symbol in the first file input is given priority. |
||
Multiple object files containing more than one entry symbol definition were input. Only the entry symbol in the first file input is effective. |
||
Sections with the same name but different boundary alignments were input. Only the largest boundary alignment specification is effective. |
||
Sections with the same name but different attributes were input. If they are an absolute section and relative section, the section is treated as an absolute section. If the read/write attributes mismatch, both are allowed. |
||
Common symbols or defined symbols with different sizes were input. A defined symbol is given priority. In the case of two common symbols, the symbol in the first file input is given priority. |
||
The attribute of symbol in file does not match the attribute of the same-name symbol in other files. |
||
Section alignment in option "aligned_section" is small : "section" |
||
Since the boundary alignment value specified for aligned_section is 16 which is smaller than that of section, the option settings made for that section are ignored. |
||
Optimization is not available when parentheses "( )" are specified in the start option. Optimization has been disabled. |
||
Cannot optimize "file"-"section" due to multi label relocation operation |
||
A section having multiple label relocation operations cannot be optimized. Section section in file has not been optimized. |
||
Cannot generate effective bls file for compiler optimization |
||
An invalid bls file was created. This optimization is not available even if optimization of access to external variables (map option) is specified for compilation. |
||
The optimization of access to external variables (map option) in the compiler has the following restriction. Check if this restriction is applicable and modify the section allocation. Access to external variables cannot be optimized in some cases if a data section is allocated immediately after a data section when the base option is specified for compilation. Note: The bls file indicates the external symbol allocation information file. It contains the information to be used for the map option of the compiler. |
||
There is no stack section, and so consistency of the stack size specified by the stack option on compiling cannot be checked. |
||
To check the consistency of the stack size on compiling, the goptimize option needs to be specified on compiling and assembling. |
||
The stack section size exceeded the stack size specified by the stack option on compiling. |
||
Either change the option used on compiling, or change the program so as to reduce the use of the stack. |
||
Different values for stack size are specified for multiple files. |
||
Input file was compiled with option "smap" and option "map" is specified at linkage |
||
The file with smap specification should not be compiled with the map option specification in the second build processing. |
||
No SYNCP instruction may be allocated at the location of the exception handler for the exception source name. |
||
See "11.4 Tool for Confirming SYNCP Instruction Insertion at the Beginning of Exception Handler". |