cppcheck/tools
Oliver Stöneberg 71cdacdc97
fixed missing location for `valueFlowMaxIterations` debug warning / also added it to daca server overview (#4664)
2022-12-30 21:20:00 +01:00
..
test
triage triage tool: handle reports when cppcheck is run on local packages 2022-12-01 06:34:23 +01:00
triage_py Typos found by running "codespell" (#4578) 2022-11-09 22:52:03 +01:00
CMakeLists.txt replaced `if(MATCHES)` with `if(STREQUAL)` (#4263) 2022-07-11 10:46:18 +02:00
ci.py use python3 on debians too (#3812) 2022-11-03 22:14:30 +01:00
compare.cs
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
dmake.cpp use `const_iterator` where possible (#4662) 2022-12-30 15:13:47 +01:00
dmake.sln
dmake.vcxproj Fix MSVC build and some warnings (#3334) 2021-07-16 21:55:12 +02:00
donate-cpu-server.py fixed missing location for `valueFlowMaxIterations` debug warning / also added it to daca server overview (#4664) 2022-12-30 21:20:00 +01:00
donate-cpu.py donate-cpu: fixed interrupted `main` branch compilation (#4643) 2022-12-18 19:50:22 +01:00
donate_cpu_lib.py donate-cpu: fixed interrupted `main` branch compilation (#4643) 2022-12-18 19:50:22 +01:00
extract_and_run_more_tests.sh
extracttests.py use python3 on debians too (#3812) 2022-11-03 22:14:30 +01: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
git-pre-commit-cppcheck
listErrorsWithoutCWE.py use python3 on debians too (#3812) 2022-11-03 22:14:30 +01:00
matchcompiler.py use python3 on debians too (#3812) 2022-11-03 22:14:30 +01:00
parse-glibc.py use python3 on debians too (#3812) 2022-11-03 22:14:30 +01:00
readme.md
reduce.py use python3 on debians too (#3812) 2022-11-03 22:14:30 +01:00
run-coverity.sh run-coverity: updated coverity tool 2022-02-18 19:55:45 +01:00
run_more_tests.sh updated CI to latest ubuntu and clang (#4004) 2022-05-22 15:27:32 +02:00
test-my-pr.py test-my-pr, mark --c-only and --cpp-only mutually exclusive (#4628) 2022-12-11 19:41:21 +01:00
test_donate_cpu_lib.py donate-cpu: small `LibraryIncludes` regular expression improvements / fixed/improved tests (#4473) 2022-09-16 18:59:53 +02:00
test_donate_cpu_server.py refs #10700 - donate-cpu-server.py: added query parameter `pkgs` to some reports to request a list of affected packages (#3743) 2022-09-29 21:55:44 +02:00
test_matchcompiler.py use python3 on debians too (#3812) 2022-11-03 22:14:30 +01:00
test_reduce.py Typos found by running "codespell" (#4260) 2022-07-10 22:40:05 +02: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
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.