SLAU131V October 2004 – February 2020
The syntax for invoking the absolute lister is:
| abs430 [-options] input file |
| abs430 | is the command that invokes the absolute lister. | |
| options | identifies the absolute lister options that you want to use. Options are not case sensitive and can appear anywhere on the command line following the command. Precede each option with a hyphen (-). The absolute lister options are as follows: | |
| -e | enables you to change the default naming conventions for filename extensions on assembly files, C source files, and C header files. The valid options are:
|
|
| The . in the extensions and the space between the option and the extension are optional. | ||
| -q | (quiet) suppresses the banner and all progress information. | |
| input file | names the linked object file. If you do not supply an extension, the absolute lister assumes that the input file has the default extension .out. If you do not supply an input filename when you invoke the absolute lister, the absolute lister prompts you for one. | |
The absolute lister produces an output file for each file that was linked. These files are named with the input filenames and an extension of .abs. Header files, however, do not generate a corresponding .abs file.
Assemble these files with the --absolute_listing assembler option as follows to create the absolute listing:
cl430 --absolute_listingfilename.abs
The -e options affect both the interpretation of filenames on the command line and the names of the output files. They should always precede any filename on the command line.
The -e options are useful when the linked object file was created from C files compiled with the debugging option (--symdebug:dwarf compiler option). When the debugging option is set, the resulting linked object file contains the name of the source files used to build it. In this case, the absolute lister does not generate a corresponding .abs file for the C header files. Also, the .abs file corresponding to a C source file uses the assembly file generated from the C source file rather than the C source file itself.
For example, suppose the C source file hello.csr is compiled with the debugging option set; the debugging option generates the assembly file hello.s. The hello.csr file includes hello.hsr. Assuming the executable file created is called hello.out, the following command generates the proper .abs file:
abs430 -ea s -ec csr -eh hsr hello.out
An .abs file is not created for hello.hsr (the header file), and hello.abs includes the assembly file hello.s, not the C source file hello.csr.