cppcheck/tools
Oliver Stöneberg 54d621555d
scan GUI sources with clang-tidy in CI (#3233)
* build UI dependencies before running clang-tidy

* clang-tidy.yml: enabled GUI sources and build some dependencies for clang-tidy

* work around missing dependency for Qt install step
2021-10-31 20:15:32 +01:00
..
test
triage scan GUI sources with clang-tidy in CI (#3233) 2021-10-31 20:15:32 +01:00
CMakeLists.txt added clang-tidy to CI (#3218) 2021-04-18 21:51:47 +02:00
ci.py
compare.cs tools/compare.cs: changed format for error message 2018-02-15 15:17:04 +01:00
compare_ast_symdb.py extended the Python script checks in the CI and adjusted some scripts (#3186) 2021-03-31 22:09:42 +02:00
creduce.py Add creduce.py script to run creduce (#3341) 2021-07-18 07:51:01 +02:00
daca2-download.py
daca2-getpackages.py some Python cleanups based on PyCharm inspections (#2999) 2021-01-31 14:27:11 +01:00
dmake.cpp Format with uncrustify (#3388) 2021-08-07 20:51:18 +02:00
dmake.sln
dmake.vcxproj Fix MSVC build and some warnings (#3334) 2021-07-16 21:55:12 +02:00
donate-cpu-server.py donate-cpu-server.py: another function compression improvement for stack trace overview in crash report (#3520) 2021-10-24 11:01:48 +02:00
donate-cpu.py various daca@home client cleanups (#3161) 2021-03-06 12:34:12 +01:00
donate_cpu_lib.py donate_cpu_lib.py: fixed detection of ThreadExecutor error (#3521) 2021-10-24 11:02:51 +02:00
extract_and_run_more_tests.sh fixed/excluded some shellcheck warnings and actually fail the build when something is found (#3068) 2021-01-20 18:43:49 +01:00
extracttests.py Fix for 6597: false negative: uninitialized variable usage not detected (ValueFlow , multi variables) (#3535) 2021-10-30 22:13:58 +02:00
generate_and_run_more_tests.sh Fix for 6597: false negative: uninitialized variable usage not detected (ValueFlow , multi variables) (#3535) 2021-10-30 22:13:58 +02:00
generate_cfg_tests.cpp Format with uncrustify (#3388) 2021-08-07 20:51:18 +02:00
git-pre-commit-cppcheck
listErrorsWithoutCWE.py
matchcompiler.py Matchcompiler parse all Match|simpleMatch on the same line (#2993) 2020-12-31 19:28:06 +01:00
parse-glibc.py
readme.md tools/readme.md: Remove astyle_client description (#3115) 2021-02-07 09:03:37 +01:00
reduce.py
run-coverity.sh fixed/excluded some shellcheck warnings and actually fail the build when something is found (#3068) 2021-01-20 18:43:49 +01:00
run_more_tests.sh Fix for 6597: false negative: uninitialized variable usage not detected (ValueFlow , multi variables) (#3535) 2021-10-30 22:13:58 +02:00
test-my-pr.py various daca@home client cleanups (#3161) 2021-03-06 12:34:12 +01:00
test_matchcompiler.py Matchcompiler parse all Match|simpleMatch on the same line (#2993) 2020-12-31 19:28:06 +01:00
test_showtimetop5.sh moved more tests from Travis to GitHub actions (#3201) 2021-04-09 07:47:11 +02:00
testrunnerify_code.sh
times-tags.sh new default branch is main 2020-06-15 20:04:57 +02:00
times-vs.py
times.c
times.sh
trac-keywords.py extended the Python script checks in the CI and adjusted some scripts (#3186) 2021-03-31 22:09:42 +02:00

readme.md

Cppcheck developer and build tools

* tools/matchcompiler.py

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.

* tools/dmake.cpp

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

* tools/reduce.py

Script that reduces code for a hang/false positive.

* tools/times.sh

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

* tools/donate-cpu.py

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

* tools/test-my-pr.py

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

* tools/triage

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.