1.2. Development Flow Differences Between armcl and tiarmclang

There are a few significant differences in terms of development flow behavior between the tiarmclang and armcl compilers. These include the following:

• The linker is invoked automatically by default by the tiarmclang compiler

  The tiarmclang compiler will invoke the linker automatically by default, whereas the armcl must be told to invoke the linker via the armcl’s --run_linker (-z) option. Further details about how to manage the linker invocation from the tiarmclang command-line can be found in the Using the tiarmclang Compiler and Linker section of the tiarmclang Getting Started Guide.

• The tiarmclang compiler does not support an interlist option on the compiler command line

  Unlike the armcl compiler, which provides -s, -ss, and -os options to instruct the compiler to generate an interlisted assembly source file, the tiarmclang does not support an interlisting option on the compiler command-line. Instead, when a C/C++ source file is compiled with debug enabled, the tiarmobjdump utility can be used with its -S option on the compiler-generated object file to produce disassembled object code with C/C++ source lines interlisted.

• The tiarmclang compiler will stop compilation after generating assembly source when the -S option is specified

  The tiarmclang compiler supports a -S option that allows you to keep the compiler-generated assembly file, but unlike the armcl’s -k option, the tiarmclang’s -S option will cause the compiler to halt immediately after generating the assembly file. When -S is used, an object file will not be written by the compiler.

• The tiarmclang compiler does not support altering the file extension of compiler-generated files

  The tiarmclang compiler does not support options to alter the file extension of compiler generated files. For more details about which armcl option do not have analogous tiarmclang options, please see the Mapping armcl Command-Line Options to tiarmclang chapter of this migration guide.