cppcheck/tools
Sebastian 4ac1500c9f
Donate CPU: Add scripts under /test for testing (#1624)
Indirectly the scripts (at first the server test script) also document what needs to be done to setup a (local) server.
The productive client script can be used by everyone who wants to support daca@home, not only for testing. But i still think it is good to have it under /test to not lose too much clarity / lucidity in the /tools directory.
2019-01-26 11:40:02 +01:00
..
test Donate CPU: Add scripts under /test for testing (#1624) 2019-01-26 11:40:02 +01:00
triage triage tool: Add "Load from clipboard" functionality (#1599) 2019-01-14 17:49:10 +01:00
ci.py
clang-ast.cpp clang-ast: print constructors and destructors 2018-04-30 15:42:40 +02:00
compare-ast-clang-and-cppcheck.py some small *.py script cleanup (#1328) 2018-08-05 20:36:21 +02:00
compare.cs tools/compare.cs: changed format for error message 2018-02-15 15:17:04 +01:00
daca-test-patch.sh Added script that tests a patch with daca 2018-08-04 09:42:55 +02:00
daca2-download.py
daca2-getpackages.py Add daca2-getpackages.py 2019-01-03 11:42:32 +01:00
daca2-logs2git.sh
daca2-report.py daca2-report: use 'diff' tool 2018-08-14 17:49:27 +02:00
dmake.cpp Clean up redundant actions in travis jobs (#1563) 2019-01-05 11:12:32 +01:00
dmake.sln dmake: Fix windows project and build (#1091) 2018-02-17 06:31:12 +01:00
dmake.vcxproj dmake: Fix windows project and build (#1091) 2018-02-17 06:31:12 +01:00
donate-cpu-server.py donate-cpu-server.py: Fix that results of package "crash" can not be … (#1620) 2019-01-24 12:02:45 +01:00
donate-cpu.py Detect X11 and Motif library in daca 2019-01-25 21:47:16 +01:00
extract_and_run_more_tests.sh
extracttests.py
generate_and_run_more_tests.sh
generate_cfg_tests.cpp generate_cfg_tests: fix argument count 2018-03-19 20:46:55 +01:00
git-pre-commit-cppcheck Missing return value in git-pre-commit-cppcheck (#1382) 2018-09-21 04:56:53 +02:00
listErrorsWithoutCWE.py
matchcompiler.py Fix typos (#1568) 2019-01-06 17:15:57 +01:00
parse-glibc.py
pr.py tools/pr.py: minor tweak 2018-11-20 06:36:08 +01:00
readme.md
reduce.cpp Fix Cppcheck missingOverride warnings 2019-01-13 13:22:36 +01:00
reduce.py Add executable bit to reduce.py 2018-03-21 09:13:26 +01:00
run-coverity.sh Updated run-coverity.sh script 2018-05-05 15:23:35 +02:00
run_more_tests.sh tools/run_more_tests.sh: Fixed comment 2018-02-02 11:27:38 +01:00
test_matchcompiler.py
test_showtimetop5.sh
testrunnerify_code.sh
times-tags.sh
times-vs.py
times.c tools: allow short SHA1 longer than 7 (#1399) 2018-09-28 19:04:39 +02:00
times.sh
trac-keywords.py python formatting. Run autopep8 and replace tabs with spaces. 2018-02-13 09:26:11 +01: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 SRCDIR=build

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.cpp

Cppcheck tool that reduces code for a hang/false positive. To build the tool run:

$ cd path/to/cppcheck
$ make reduce

* tools/times.sh

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