Introducing the new analysis type TraceVisualizer that extracts measured task executions from given trace data and displays them in a flame graph.
Improved support for Unicode file names in all tools. On Unices, it is assumed that the locale is set to a UTF-8 variant for the wanted language.
tor
, tovvcp
,..)operational-requirements-*.htm
has been renamed into tor_*.htm
verification-test-plan-*.htm
has been renamed into tovvcp_*.htm
qk_computation_entries | all architectures |
qk_ais2_expression_number_of_elements | all architectures |
qk_setting_psw_io | TriCore |
qk_ais2_program_point_offset_return
qk_ais2_program_point_offset_call_pp
qk_ais2_program_point_offset_read
qk_ais2_program_point_offset_unconditional
qk_ais2_program_point_offset_write
qk_ais2_attribute_predefined
to check for the new immutable attribute target_type
.qk_ais2_area_properties_copied
to additionally check for multiple area copy annotations
to the same target address.--timeout
time to the command line of QSK tool runs
(change of qualified workflow).qk_setting_expected_result
to explicitly test
AIS2 language components in the expected result expression.entries(@groupid)
that returns
the number of analyses in the group.trapEntry(<TCN>)
”,
to determine the address of a trap handler associated with the given trap class number (TCN).instruction "main" instruction -> 8 bytes { ... }and instead needs to be written as:
instruction "main" { instruction -> 8 bytes { ... } }
area ... count accesses
” annotation
is now also available for TimeWeaver analyses. In addition to global
statistics, per-block statistics are output to the XML report file
and included in the call graph.instruction <pp> { stack <stack_name> alignment: <n> bytes; }
routine/loop takes xxx cycles
” annotations.
The tool now honors program exits in routines/loops cut out with such annotations
even though all other effects are still ignored.isa-arm: Warning #3177: In "minmax.c", line 14:
In routine 'min', at address 0x800000ad8:
In "<suite>/bugs/31872/test.ais", line 2:
Instruction 'b 0x800000acc <0x800000acc>' is considered to be a regular call but might rather be a tail call.
This could be caused by an annotation.
isa-arm: Warning #3177: In "scenarios_a3.c", line 242:
In routine 'ISR2_minmax', at address 0x800000f04:
In "<suite>/bugs/31872/test.ais", line 7:
Instruction 'bl 0x800000adc <max>' is considered to be a tail call but might rather be a regular call.
This could be caused by an annotation.
nullptr
in type domain.fcall
/fret
and call
/ret
on TriCore.bctr
”
to return to their callers if the instruction has been manually annotated
to be a return instruction..opd
section.e_cmph
, se_cmph
, e_cmph16i
,
e_cmphl
, se_cmphl
, and e_cmphl16i
.