
Hitachi Embedded Workshop User Manual
158
2.13
Floating-Point Data
Floating-point numbers can be used for the following real-number data, which makes floating-point data
processing easier. The following data can be specified for floating-point data:
Data in the [Set Break] dialog box when the break type is set to [Break Data] or [Break Register]
Data in the [Memory] window
Data in the [Fill Memory] dialog box
Data in the [Search Memory] dialog box
Input data in the [Register] dialog box
The floating-point data format conforms to the ANSI C standard.
In the simulator/debugger, the rounding mode for floating-point decimal-to-binary conversion can be selected in
the [Simulator System] dialog box. One of the following two modes can be selected:
Round-to-nearest (RN)
Round-to-zero (RZ)
If a denormalized number is specified for binary-to-decimal or decimal-to-binary conversion, it is converted to
zero in RZ mode, and left as a denormalized number in RN mode. If an overflow occurs during decimal-to-
binary conversion, the maximum floating-point value is returned in RZ mode, and the infinity is returned in RN
mode.
2.14
Display of Function Call History
The simulator/debugger displays the function call history in the [Stack Trace] window when simulation stops,
which enables program execution flow to be checked easily. Selecting a function name in the [Stack Trace]
window displays the corresponding source program in the [Source] window. This allows the function that has
called the current function to also be checked.
The displayed function call history is updated in the following cases:
When simulation stops due to the break conditions described in section 2.16, Break Conditions.
When register values are modified while simulation stops due to the above break conditions.
While single-step execution is performed.
For details, refer to section 4.13, Viewing the Function Call History.
2.15
Performance Measurement
The simulator/debugger has the profiler function and performance analysis function for performance
measurement of the user program.
2.15.1
Profiler
The profiler function displays the memory address and size allocated to functions and global variables, the
number of function calls, and the profile data for the entire user program. The profile data displayed differs
according to the CPU.
Profile information is displayed in list, tree, and chart formats.
Profile information is useful in optimizing user programs by reducing the size and putting the most frequently
called functions in-line.