Compiler Settings

Can't find your question? Click here to contact us!

How do I optimize performance with ASH WARE's simulator tools?
What are ASH WARE's ETEC Compiler settings?
What are Byte Craft Limited's ETPU_C Compiler settings on eTPU targets?
What are Freescale's TPU MASM settings on TPU targets?
What are the DIAB DATA toolset settings on CPU32 targets?
What are the GNU toolset options on CPU32 targets?
What are the INTROL toolset options on CPU32 targets?
What are the INTROL toolset settings on CPU16 targets?

How do I optimize performance with ASH WARE's simulator tools?

For each vendor's toolset consisting of compiler, assembler, and linker there are settings that will best optimize performance with the ASH WARE development tools. These generally specify inclusion of debugging information, the level of optimization (in certain cases reducing the amount of optimization improves source level debugging) and the stack frame structure. Note that with regards to the eTPU, the ASH WARE ETEC eTPU/eTPU2 C Compiler is designed to work seamlessly with the eTPU and eTPU2 Simulators.

What are ASH WARE's ETEC Compiler settings?

ETEC generally outputs everything needed for debug and host integration, but we do recommend using the -lst and -map options on the linker to output listing and a map file that can provide useful information.

For use with Lauterbach, we recommend disabling the extended entry table debugging information that is output by default, as Lauterbach does not support it. This is done with linker option -etdbg-.

What are Byte Craft Limited's ETPU_C Compiler settings on eTPU targets?

Version(s) Supported
All
Assembler Options
Not applicable
Compiler Options
Compiler options listed are for command line only
+l Generate a listing file
+e Generate an error file
+q Suppress dialog box
Linker Options
Not Applicable
File Type
Byte Craft Limited's Code (COD) file
What are Freescale's TPU MASM settings on TPU targets?

Version(s) Supported
3.1, 3.33, 4.01, 4.03, 4.04, 5.00
Assembler Options
Does not matter.
File Type
Freescale defined, ".LST" file.
What are the DIAB DATA toolset settings on CPU32 targets?

Assembler Options
-tCPU32EScross Generate code for CPU32 target.
Compiler Options
-tCPU32EScross Generate code for CPU32 target.
-g Generate symbolic debugging information for source-level debugging.
Linker Options
-tCPU32EScross Link code for the CPU32 target. -Xcoff Generate a COFF output file. -o Write output to the specified filename. An e68 file suffix is the default MtDt search option.
File Type
Common Object File Format (COFF) file.
Notes
The DIAB DATA assembler does not generate line numbers. Standard source level code flow commands such as single step and goto cursor will therefore not work correctly with the assembler. The compiler works correctly as it does not have this limitation.
What are the GNU toolset options on CPU32 targets?

Assembler Options
-O0 Disable optimization; simplifies debugging but is not required
-gcoff Write output in COFF format.
-mcpu32 Create CPU32 compatible code.
-Wall Enable all warnings.
-ansi Support ANSI C, but not any GNU extensions. (Not required.)
Compiler Options
Same as assembler (see above).
Linker Options
-m68020
-Wl,-n ?? needed?
-T
Specifies linker script file used to control link.
-Wl,Map= Write link map to filename. -nostartfiles ??
File Type
Common Object File Format (COFF) file.
Version(s) Supported
2.91.1
What are the INTROL toolset options on CPU32 targets?

Version(s) Supported
4.00.0.4
Assembler Options
-l Add line number information. Required for source-level debugging of assembly language programs.
Compiler Options
-g68 Generates code for the 683xx family
-gg Generate symbolic debugging information for source-level debugging.
-ggn Disable deferred stored from being generated by the code generator
Linker Options
-g68link Links code for the 683xx family
-o .e68 Generates output file with the e68 suffix. An e68 file suffix is the default MtDt search option.
File Type
Introl Common Object File Format (ICOFF) file.
What are the INTROL toolset settings on CPU16 targets?

Version(s) Supported
4.00.0.4
Assembler Options
-l Add line number information. Required for source-level debugging of assembly language programs.
Compiler Options
-g16 Generates code for the 68HC16 family.
-gg Generate symbolic debugging information for source-level debugging.
Linker Options
-g16link Links code for the 68HC16 family.
-o .e16 Generates output file with the e16 suffix. Using an e16 file suffix allows MtDt's default search options to work.
File Type
Introl Common Object File Format (ICOFF) file.