Assembler Listing File Format
Cross-reference Format
MOTOROLA
DSP ASSEMBLER REFERENCE MANUAL
For More Information On This Product,
Go to: www.freescale.com
D-3
gram they would be shown here, as well as define symbols and their corresponding sub-
stitution strings. Next the symbol table is output, sorted by symbol name. The symbol table
data includes the symbol type (integer, floating point), its value, the section where it was
defined if applicable, and any attributes it may have (LOCAL, GLOBAL, SET).
Figure D-3 contains an annotated Assembler listing line showing virtually every possible
listing field. The significance of some fields may require further explanation. The macro
definition/expansion column will contain a plus sign (
+
) during macro expansion. It will
contain a lower case
‘m
’ during macro definition, and a lower case
‘d
’ during data constant
expansion (the
CEX
option used with the
DC
directive). When a nested macro is expand-
ed, this column will contain both a lower case
‘m
’ and a plus sign. A lower case ‘
i
’ in this
column indicates that the line has been skipped as a result of an
IF-THEN-ELSE
directive
sequence. A lower case ‘
p
’ means that the line was automatically generated by the As-
sembler, ordinarily to introduce pipeline delay.
D.3
CROSS-REFERENCE FORMAT
The Assembler will optionally generate a cross-reference listing of all symbols used in the
source program. This can be done by using the
CEX
option of the
OPT
directive (Chapter
6). The cross-reference listing for the above sample program is shown in Figure D-2. It
contains a sorted table of symbols, each one followed by a list of line numbers in the
source listing where a reference to the symbol occurred. Line numbers followed by an as-
terisk (
*
) indicate the line where the symbol was defined.
D.4
MEMORY UTILIZATION REPORT FORMAT
The Assembler can optionally record and report allocation and usage of the separate
memory spaces of the target DSP. This is done with the
MU
option of the
OPT
directive
(Chapter 6). A memory utilization report is a memory map showing data allocation, code
generation, and unused memory areas along with associated label, section, and overlay
information, if available.
Figure D-4 shows the memory utilization report for the Assembler source in Figure D-5.
The individual X, Y, L, and P memory spaces are reported separately. The starting and
ending addresses, length, type, and any label, section, or overlay data are display for
each reported block. The blocks are delimited by the occurrence in the source of either a
data allocation directive (
BSC
,
DC
,
DS
,
DSM
,
DSR
) or an
ORG
directive.
In the X memory report of Figure D-4 the first reported block is an uninitialized area of
1024 words. This corresponds to the first
DS
directive in Figure D-5, which reserves 1024
words of memory in X data space. The next block of memory in X data space is the overlay
code for the FIR filter. It begins immediately after the first block and is ten words long.
The type column shows what kind of code or data has been generated, as well as indicat-
ing that a block is unused. In the line corresponding to the first
DS
directive in the source,
the type is DATA to indicate that it is an uninitialized data area. There are other types for
initialized data, code, and modulo and reverse carry buffers. For example, the second
F
Freescale Semiconductor, Inc.
n
.