The following list details the limitations of the trace view data visualization feature:
- In certain cases, data repeats twice in the timeline. Data repeats because the very-long instruction word (VLIW) CPU fetches data from two different load ports in the same cycle. Memory arbitrates the two load data in two consecutive cycles, so that same data repeats in the timeline.
- 64-bit non-vector window data types display as two 32-bit high and low
values.
Example 1: an unsigned, 64-bit integer
0x0000000100000002displays as 2L and 1H separately. L and H represent low and high 32 bits.Example 2: a complex 32-bit value where the real 32 bits display first, followed by the imaginary 32 bits.
- The
input_pktstream/output_pktstreamdata type displays in integer format. - Trace view data visualization does not support the int64 data type used in a templated class.
- If the AI Engine compiler inlines kernel functions, they are not visible in the trace.
- Inlined kernel function I/O ports are not visible in the trace.