-F (-Fh, -F1, -F1o, -F2, -F2o,-F6, or -F7): Object-File Format

OUTPUT

Application

  -F(1|1o|2|2o|6|7|h)
  
  

h: HIWARE object-file format

1: ELF/DWARF 1.1 object-file format

1o: compatible ELF/DWARF 1.1 object-file format

2: ELF/DWARF 2.0 object-file format

2o: compatible ELF/DWARF 2.0 object-file format

6: strict HIWARE V2.6 object-file format

7: strict HIWARE V2.7 object-file format

  -Fh
  
  

  
  __HIWARE_OBJECT_FILE_FORMAT__
  
  

__ELF_OBJECT_FILE_FORMAT__

None

The Compiler writes the code and debugging info into an object file after compilation.

The Compiler uses a HIWARE-proprietary object-file format when the -Fh, -F6 or -F7 options are set.

The HIWARE Object-file Format ( -Fh) has the following limitations:

• The type char is limited to a size of 1 byte.
• Symbolic debugging for enumerations is limited to 16-bit signed enumerations.
• No zero bytes in strings are allowed (a zero byte marks the end of the string).

The HIWARE V2.7 Object-file Format (option -F7) has some limitations:

• The type char is limited to a size of 1 byte.
• Enumerations are limited to a size of 2 bytes and must be signed.
• No symbolic debugging for enumerations.
• The standard type short is encoded as int in the object-file format.
• No zero bytes in strings allowed (a zero byte marks the end of the string).

The Compiler produces an ELF/DWARF object file when the -F1 or -F2 options are set. This object-file format may also be supported by other Compiler vendors.

In the Compiler ELF/DWARF 2.0 output, some constructs written in previous versions did not conform to the ELF standard because the standard was not clear enough in this area. Because old versions of the simulator or debugger (V5.2 or earlier) are not able to load the corrected format, the old behavior can still be produced by using -f2o instead of -f2. Some old versions of the debugger (simulator or debugger V5.2 or earlier) generate a GPF when a new absolute file is loaded. To use the older versions, use -f2o instead of -f2. New versions of the debugger can load both formats correctly. Also, some older ELF/DWARF object file loaders from emulator vendors may require you to set the -F2o option.

The -F1o option is only supported if the target supports the ELF/DWARF 1.1 format. This option is only used with older debugger versions as a compatibility option. This option may be discontinued in the future. We recommend that you use -F1 instead.

We recommend that you use the ELF/DWARF 2.0 format instead of the ELF/DWARF 1.1. The 2.0 format is much more generic. In addition, it supports multiple include files plus modifications of the basic generic types (for example, floating point format). Debug information is also more robust.