
Hitachi Embedded Workshop User Manual
159
When using the profile information saved in a file, it is possible to optimize user programs based on dynamic
information using the optimizing linkage editor.
For details, refer to section 4.12, Viewing the Profile Information, and section 4.2.3, Optimize Option Profile in
the Optimizing Linkage Editor User's Manual.
2.15.2
Performance Analysis
The performance analysis function displays the number of execution cycles and function calls for the specified
function in the user program. Since performance data for only the specified function is acquired, simulation can
be done faster. For details, refer to section 4.16, Analyzing Performance.
2.16
Pseudo-Interrupts
The simulator/debugger can generate pseudo-interrupts during simulation in the following two ways:
1. Pseudo-interrupts generated by break conditions
A pseudo-interrupt can be generated using a break command to specify [Interrupt] as the action when a break
condition is satisfied. For details, refer to “Specifying the Action at Break” in section 4.15.2, Setting a
Breakpoint.
2. Pseudo-interrupts generated from the [Trigger] window
A pseudo-interrupt can be generated by clicking a button in the [Trigger] window. For details, refer to section
4.20, Generating a Pseudo-Interrupt Manually.
If another pseudo-interrupt occurs between a pseudo-interrupt occurrence and its acceptance, only the interrupt
that has a higher priority can be processed.
Note: In the pseudo-interrupts, whether an interrupt is accepted is determined by interrupt information
[Priority], not the vector number. Note that when H'8 is specified as the priority level of an
interrupt, that interrupt is always accepted. The simulator/debugger does not simulate the
operation of the interrupt controller.
2.17
Coverage
The simulator/debugger acquires instruction coverage information during instruction execution within the
address range specified by the user.
The status of each instruction execution can be monitored through the instruction coverage information. In
addition, this information can be used to determine which part of a program has not been executed.
The [Coverage] window displays the acquired instruction coverage information:
The instruction coverage information can also be displayed in the [Source] window by highlighting the column
corresponding to the source line of the executed instruction.
The instruction coverage information can be saved in or loaded from a file. Only a file in the .COV format can
be loaded.
For details, refer to section 4.17, Acquiring Code Coverage.