
Defining Areas for Profiling
10-5
Profiling Code Execution
10.3 Defining Areas for Profiling
Within the profiling environment, you can collect statistics on three types of
areas:
-
Individual lines in C or disassembly
-
Ranges in C or disassembly
-
Functions in C only
To identify any of these areas for profiling, mark
the line, range, or function. You
can disable areas so that they won’t affect the profile data, and you can reen-
able areas that have been disabled. You can also unmark areas that you are
no longer interested in.
The mouse is the simplest way to mark, disable, enable, and unmark tasks.
The pulldown menus also support these tasks and more complex tasks.
The following subsections explain how to mark, disable, reenable, and unmark
profile areas by using the mouse or the pulldown menus. The individual com-
mands are summarized in
Restrictions of the profiling environment on page
10-3.
Restrictions on profiling areas are summarized on page 10-12.
Marking an area
Marking an area qualifies it for profiling so that the debugger can collect timing
statistics about the area.
Remember, to display C code, use the FILE or FUNC command; to display dis-
assembly, use the DASM command.
Notes:
1) Marking an area in C
does not mark the associated code in disassembly.
2) Areas can be nested; for example, you can mark a line within a marked
range. The debugger will report statistics for both the line and the func-
tion.
3) Ranges cannot overlap, and they cannot span function boundaries.
Summary of Contents for TMS320C6 Series
Page 10: ...x ...
Page 20: ...xx ...
Page 118: ...4 20 ...
Page 144: ...6 16 ...
Page 164: ...7 20 ...
Page 170: ...8 6 ...
Page 284: ...B 18 ...
Page 290: ...C 6 ...