The assembler supports several directives that the TMS320C6000 C/C++ compiler uses for symbolic debugging.

These directives are not meant for use by assembly-language programmers. They require arguments that can be difficult to calculate manually, and their usage must conform to a predetermined agreement between the compiler, the assembler, and the debugger. This appendix documents these directives for informational purposes only.

A.1 DWARF Debugging Format

A subset of the DWARF symbolic debugging directives are always listed in the assembly language file that the compiler creates for program analysis purposes. To list the complete set used for full symbolic debug, invoke the compiler with the --symdebug:dwarf option, as shown below:

cl6x --symdebug:dwarf --keep_asm input_file

The --keep_asm option instructs the compiler to retain the generated assembly file.

To disable the generation of all symbolic debug directives, invoke the compiler with the -symdebug:none option:

cl6x --symdebug:none --keep_asm input_file

The DWARF debugging format consists of the following directives:

• The .dwtag and .dwendtag directives define a Debug Information Entry (DIE) in the .debug_info section.
• The .dwattr directive adds an attribute to an existing DIE.
• The .dwpsn directive identifies the source position of a C/C++ statement.
• The .dwcie and .dwendentry directives define a Common Information Entry (CIE) in the .debug_frame section.
• The .dwfde and .dwendentry directives define a Frame Description Entry (FDE) in the .debug_frame section.
• The .dwcfi directive defines a call frame instruction for a CIE or FDE.

A.2 Debug Directive Syntax

Table A-1 is an alphabetical listing of the symbolic debugging directives. For information on the C/C++ compiler, refer to the TMS320C6000 Optimizing Compiler User's Guide.