This new subsection of every WCET analysis allows viewing a table with cumulative WCET contributions for each routine.
Instructions annotated in the AIS file are now highlighted throughout the GUI:
The highlighted instructions are also linked to the corresponding line in the AIS file.
Syntax highlighting in the AIS editor now uses a color scheme that is much easier on the eye.
a³ now features an all-new Global Preferences dialog, accessible via the menu “Project” → “Preferences…”. Here, you can customize a multitude of settings such as keyboard shortcuts, toolbars, fonts and colors used in the various views, and more. You can also restore the default settings at any time.
The new Configurations view enables easy creation of and switching between multiple analysis configurations. A new configuration can be derived from any existing one. Its settings can then be conveniently edited right in the Configurations view rather than at their respective locations throughout the user interface.
The a³ GUI now provides a visual feedback for any background activity (extraction of symbols, running analyses, etc). The current activity and its progress is reported in a small widget that appears in the bottom left corner of the a³ window.
a³ now features a greatly simplified email-based license request process. In the License dialogue box, you can now simply click on the button “Request license…” and your favorite email program will open with a pre-composed message to our support team. The message will contain all the information we will need to issue a license for your machine, so you can simply click “Send” and lean back.
For convenience reasons, the tool chain no longer floods the user with identical messages, such as write accesses into read-only memory regions. This behavior is configurable under “Configuration” → “Analyses” → “General” → “All Analyses” → “Reduce number of identical messages”.
Control files generated by the old aiT GUI can now be imported under “Analyses” → “Overview” → “Import control file”.
a³ now officially supports the XTC exchange format. The user may generate XTC requests and import XTC responses. So far only T1 is supported. T1 can measure unknown loop bounds (and, in the future, targets of unresolved computed calls).