TASKING TriCore v6.2r2  Inspector v1.0r1
Release Note


This release note covers the initial features of the TASKING TriCore v6.2r2 Inspector v1.0r1.


Important Notices

Tricore v6.2r2 Inspector v1.0r1 is based on TASKING VX-toolset for TriCore v6.2r2. Inspector operates identical to the VX-toolset (except for the issue detection) down to the Linker. Generation of the final executable image by the Linker has been disabled.

Components of the VX-toolset dealing with the final executable image, library sources, examples have been removed from the product.

Components modified for the issue detection have been renamed with prefix insp_ (insp_cctc, insp_cptc, insp_ctc, insp_astc, insp_ltc).

New Features in v1.0r1

Detection options

By default, Inspector detects and reports full set of supported issues. The following options allow the user to customize this set:

--ignore=<issue-id>,... - disables detection of specified issues.

--detect=<issue-id>,... - disables detection of all issues and enables detection of specified issues only.

These options are supported by the Control Program, C/C++ Compiler, Assembler and Linker. Issue ID corresponds to issue's identification on the TASKING Issue Portal.

Detection messages

Inspector indicates issue detection by producing a warning message in two possible ways:

1. Definite detection.

Reported when Inspector can guarantee by detector's construction that processed code is affected by the triggered issue. Note that the affected code may still be removed from the final executable image by subsequent optimizations or linker - this requires verification by the user.

Example: ctc W999: [25/12] [INSP] detected occurrence of issue TCVX-43464.

2. Potential detection.

Reported when the issue is triggered, but Inspector can not guarantee that the processed code has been affected. Location and/or some additional information will be reported to facilitate verification by the user.

Example: ctc W998: [10/29] [INSP] detected potential occurrence of issue TCVX-43429.

Detection by assembly comparison

Some potential detectors produce a lot of false positives. To narrow the processing, assembly comparison mode is introduced.

--detect-asm=<issue-id> - with this option Inspector only detects a single specified issue.

After initial potential detection Inspector generates two instances of assembly code - affected and not affected by the issue.

If comparison of these generated assembly files produces any meaningful difference, Inspector reports it and indicates locations of generated files for the further analysis.

Message Logging

Inspector supports separate logging of detection messages.

--insp-log=<file> - with this option all detection messages are duplicated into the specified file.

Log file is written in append mode and clearing it at the right moment is the user's responsibility

Logging mechanism supports concurrent writing for the multi-threaded build, but file locking over network is unreliable, so it shouldn't be used with a remotely located log file.

Issues detected in v1.0r1

Available detectors for each tool are also listed if --detect option is used without an argument

License Information

TASKING products are protected with TASKING license management software.

License key

You need a license key when you install a TASKING product on a computer. When you order a TASKING product from TASKING or one of its distributors, a license key will be sent to you by email or on paper.

See the Getting Started with the TASKING Inspector for TriCore guide for information on obtaining a license.

Local TASKING License Server (not applicable to evaluation licenses)

If you have ordered a TASKING product with a floating license, you can have it serviced by the Remote TASKING License Server (the most convenient solution) or through a Local TASKING License Server (in case you have no external network access for example). Consult your TASKING representative for assistance on deciding what the best setup would be for your situation.

If you like to setup up a local license server, we kindly refer you for more information to Support for TASKING License Management System (TLM) on our website. Here you can also download the Local TASKING License Server package.

It is advised that you install the Local TASKING License Server before you install products that require this server.