7.1 Fatal Errors
The following errors indicate that an internal error has occurred in the assembler. Please contact Microchip Technical Support (support.microchip.com) if any of the following errors are generated:
- A dummy instruction cannot be used!
- bad floating-point constant: exponent overflow, probably assembling junk
- bad floating-point constant: unknown error code=error_code
- C_EFCN symbol out of scope
- Can’t continue
- Can’t extend frag num. chars
- Can’t open a bfd on stdout name
- Case value val unexpected at line _line_ of file “_file_”
- emulations not handled in this configuration
- error constructing pop_table_name pseudo-op table: err_txt
- expr.c(operand): bad atof_generic return val val
- failed sanity check
- filename:line_num: bad return from bfd_install_relocation: val
- filename:line_num: bad return from bfd_install_relocation
- Inserting “name” into symbol table failed: error_string
- pic30_get_g_or_h_mode_value called with an invalid operand type
- pic30_get_p_or_q_mode_value called with an invalid operand type
- pic30_insert_dsp_writeback called with an invalid operand type
- pic30_insert_dsp_x_prefetch_operation called with an invalid offset
- pic30_insert_dsp_x_prefetch_operation called with an invalid operand type
- pic30_insert_dsp_y_prefetch_operation called with an invalid offset
- pic30_insert_dsp_y_prefetch_operation called with an invalid operand type
- invalid segment “name”; segment “name” assumed
- label “temp$” redefined
- macros nested too deeply
- missing emulation mode name
- multiple emulation names specified
- Relocation type not supported by object file format
- reloc type not supported by object file format
- rva not supported
- rva without symbol
- unrecognized emulation name ‘em’
- Unsupported BFD relocation size in bytes