To enable the analyzers to accurately analyze the source code they need to understand the behavior and capabilities of the compiler. There are many, many different vendors, architectures, targets and versions of a compiler and we use a CCT to describe this information – it is passed to the analyzer during analysis to provide optimum results. There is one CCT per language (i.e. one for C and one for C++).
CCTs fall into two types:
- Static – These have been pre-generated by the Helix QAC team for the most popular compilers such as gcc and Microsoft Visual Studio - they are shipped by default with the software. Some older static CCTs are also available for older compilers – contact support to see if they are available for your required compiler. See Static CCTs for more information.
- Automatic – To get more accurate results for your system the synchronization process can additionally interrogate your system and build a CCT as part of the synchronization – this is the preferred way to generate a CCT. See Auto CCTs for more information.