The matchcompiler.py is a build script that performs a few code transformations to .cpp files under the lib directory. These transformations are related to the use of Token::Match() function and are intended to improve code performance. The transformed files are saved on the build directory. This tool is silently used when building the code with SRCDIR=build, that is:

$ cd path/to/cppcheck
$ make MATCHCOMPILER=yes

Here is a simple example of the matchcompiler.py optimization. Suppose there is a file example.cpp under lib/:

// lib/example.cpp
void f1() {
    Token::Match(tok, "abc");
}

void f2() {
    const char *abc = "abc";
    Token::Match(tok, abc);
}

If you manually run matchcompiler.py from the main directory:

$ cd path/to/cppcheck
$ python tools/matchcompiler.py

A file example.cpp will be generated on the build directory:

// build/example.cpp
#include "token.h"
#include "errorlogger.h"
#include <string>
#include <cstring>
static const std::string matchStr1("abc");
// pattern: abc
static bool match1(const Token* tok) {
    if (!tok || !(tok->str()==matchStr1)/* abc */)
        return false;
    return true;
}
void f1() {
    match1(tok);
}

void f2() {
    const char *abc = "abc";
    Token::Match(tok, abc);
}

From this we can see that the usage of Token::Match() in f1() has been optimized, whereas the one in f2() couldn't be optimized (the string wasn't inline on the Token::Match() call). The developer doesn't need to use this tool during development but should be aware of these optimizations. Building with this optimization, cppcheck can get a boost of 2x of speed-up.

Automatically generates the main Makefile for Cppcheck (the main Makefile should not be modified manually). To build and run the dmake tool execute:

$ cd path/to/cppcheck
$ make dmake
$ ./dmake

Script that reduces code for a hang/false positive.

Script to generate a times.log file that contains timing information of the last 20 revisions.

Script to donate CPU time to Cppcheck project by checking current Debian packages.

Script to compare result of working Cppcheck from your branch with main branch.

This tool lets you comfortably look at Cppcheck analysis results for daca packages. It automatically downloads the package, extracts it and jumps to the corresponding source code for a Cppcheck message.

Script to compare the error IDs in the expected testrunner output (without executing it) with the --errorlist output. It will report missing test coverage for an ID and missing IDs in the --errorlist output.

Script that converts a Cppcheck XML results file (--xml) into a Cppcheck XML suppressions file, so that existing warnings can be suppressed as a baseline and only new warnings are reported afterwards. For each <error> in the results file that has a non-zero hash attribute, it writes a <suppress> entry with the error's id, the file of its first <location> and the hash. Usage:

$ cppcheck --xml --xml-version=2 ./src 2> results.xml
$ python tools/generate-baseline-suppressions.py results.xml suppressions.xml

The generated suppressions.xml can then be passed to Cppcheck with --suppress-xml=suppressions.xml.

Script to tweak -isystem/--sysroot/-I options in a compile_commands.json file, for example to make implicit --sysroot-relative -isystem paths explicit, convert -isystem to -I, or remove unwanted include paths. See tools/tweak-compile-commands.md for details.