aiT user interface

aiT screenshot

aiT can be combined with other analyzers from AbsInt in a single intuitive user interface.


aiT screenshot

aiT directly analyzes binary executables, so that no modification of your toolchain or the system’s operational behavior or performance is required.


aiT screenshot

aiT accepts optional user annotations for the analyzed files, such as targets of indirect function calls, upper bounds for loop iteration counts, recursion depth, code snippets that should not be analyzed, infeasible code, and so on. You can provide the annotations in a sepa­rate text file, or simply use the fully integrated annotations wizard that will generate such a file auto­ma­tically based on your input.

Annotations are only required if the information cannot be detected automatically by aiT, e.g. for dynamic program properties. The amount of required annotations is dramatically reduced by a number of advanced techniques such as automatic loop-bound and array-call recognition.

aiT screenshot

Point-and-click annotations

aiT screenshot

Sample projects with various annotations


aiT screenshot

Analysis results: the computed WCET is given in CPU cycles and microseconds. aiT-computed bounds are valid for all inputs and execution scenarios.

Double-clicking on the analysis results opens the call graph of the analyzed application.


aiT screenshot

Call graph with WCET analysis results. Each routine is annotated by its relative contribution to the overall WCET. Worst-case execution paths, infeasible calls, and recursions are automatically recognized and highlighted.

aiT also automatically determines any locations that could benefit from additional annotations, marks them for you, and even suggests the best wording for the annotation that you can then accept or modify with a couple clicks.

The routines can be interactively unfolded to inspect the control flow within them.


aiT screenshot

Control flow graph with WCET analysis results. Each edge is labeled with the maximum number of traversals in the worst case and the execution time of the basic block it originates from. Infeasible parts of the analyzed program (dead code) are grayed out.

Analysis details such as WCET contribution in different contexts can be viewed in additional information windows. Context menus enable jumping from anywhere in the graph to the corresponding line in the C or assembly code.

For each instruction, the set of all possible pipeline states can be inspected as desired.


aiT screenshot

Visualization of pipeline and cache behavior over time. Each horizontal layer corresponds to one CPU cycle. Branches in the tree represent different execution scenarios, e.g. a cache hit and a cache miss at a memory access if both cases have to be analyzed. aiT auto­matically checks all possibilities.


Sample pipeline analysis results legend (MPC5xx)

aiT for MPC5xx
  1. Start state*
  2. Intermediate state*
  3. End state*
  4. State description
  5. Flash A
  6. Flash B
  7. Memory controller
  8. L2U
  9. Fetch
  10. Dispatch
  11. Execute
  12. Write-back
  13. Decode buffer
  14. Prefetch queue
  15. History queue

* Relative to the instruction to be analyzed.


aiT screenshot

Various statistics are compiled so you can quickly identify bottlenecks and other areas of interest.

aiT screenshot

Interactive visualization of WCET contributions
per execution context

aiT screenshot

Variable usage statistics


aiT screenshot

The Sections view allows you to view all sections of the binary and inspect their content like in a hex editor. It also enables you to find out the memory content for a given address area.


aiT screenshot

An optional ValueAnalyzer add-on lets you inspect the contents of all registers and memory cells at any program point in any execution context.