HP 1630A Operating And Programming Manual page 70

Performance Analysis Measurements
Model 1630A/D/G
To define the seven routines, first change the label next to the [State Label] field to [ADDR] with the NEXT[]
key. (ADDR must be previously defined in the Format menu .) Then move the cursor to the ALL label at the
lower left corner of the display. Change this label to "FADD" . Then define the low and high addresses for this
routine. Add the remaining labels (FSUB, FMUL, FDIV, FCMP, FMOVE, FNORM) by pressing INSERT and
filling in the corresponding fields .
Next move up to the [states] field . This defines how memory accesses following opcode fetches will be
counted . In the [states] mode, the accesses will be counted individually from the opcode fetches, adding to
labels defining the memory area, if such labels exist. In the [program activity] mode, these accesses will be
counted along with the preceding opcode fetch in the range of the opcode fetch . Therefore, in the [states]
mode, stack accesses are counted as occurring at the stack location while in the [program activity] mode the
stack accesses would be counted as occurring in the location of the opcode preceding the stack accesses . For
this example, the [states] mode is used . Figure 5-1 is the State Label Overview Trace Specification for this
example measurement.
The State Label Trace samples the program activity in groups of 1024 states per sample . In between each
sample, a random delay is invoked to insure random sampling . After running the given example, the routine
F_NORM was found to consume the majority of the floating point processing time . Refer to figure 5-2 .
F_MOVE also was found to consume a great deal of processing time . By making the F_NORM and F_MOVE
routines more efficient, the module performance could be greatly improved . Therefore, a great increase in
module performance could be achieved by modifying only two of the module's routines .