Appeal No. 2001-0653
Application 08/820,736
on "storage media," which is broad enough to read on both the
computer memory or storage such as a hard disk, because it must
be stored somewhere in order to be utilized by the computer.
An example of profiling is described in Chapter 4. The
source module PTOLL.C (pp. 129-130) contains three routines:
"main()," "route66()," and "highway80()." If the area is set to
"Routines in Module," which "adds area markers for all routines
in the current module" (p. 50), Profiler will collect information
about the time spent in each routine (procedure) and the number
of execution counts each time the routine is executed, as shown
in Figure 4.1 (p. 130). Each routine is "an instrumented code
block," as claimed. (Other possible examples of "instrumented
code blocks" are a single line of code or a programming construct
such as a loop (pp. 12, 109)). The time-collection compartments
and the count-collection compartments in Figure 4.1 are "at least
one procedure specific data storage area" because they correspond
to data storage areas for time and count data that is specific to
each routine (procedure). Appellants give a similar example of
three procedures with counter areas (spec. at 18):
Therefore, if source module 1 had three procedures "main,"
"foo" and "bar," its corresponding profile data file will
have three procedure counter areas identified as "main,"
"foo" and "bar." The profile data files may be stored or
archived with their corresponding source modules for later
retrieval.
- 10 -
Page: Previous 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 Next
Last modified: November 3, 2007