cppcheck/tools
Jérémy Lefaure 08d8b2da38 git-pre-commit-cppcheck: check only added or modified source files
The regexp is written according to git-diff-index manual.
2016-05-07 19:09:13 +02:00
..
ci.py PEP8 fixes. 2015-04-20 21:11:45 +03:00
daca2-addons.py Skip another package in daca2 (gcc-arm) to avoid timeouts 2016-04-25 20:48:11 +02:00
daca2-download.py Run all Python code through autopep8 2016-01-05 13:30:32 +01:00
daca2-report.py Raise file size limit for daca2 from 100kb to 1mb 2016-01-31 21:18:50 +01:00
daca2.py daca2: don't skip insighttoolkit, it does not hang as far as I see. 2016-02-15 16:56:23 +01:00
dmake.cpp Preprocessor directives for addons 2016-01-15 12:36:35 +01:00
dmake.vcproj Tools: Update VS project file. 2011-08-11 23:40:10 +03:00
extract_and_run_more_tests.sh Testing: extract testcases, edit comparisons, run cppcheck, compare results 2015-07-22 09:52:24 +02:00
extracttests.py Cleanup Copyrights. Now all should be just for Cppcheck team. 2016-01-01 23:04:16 +01:00
generate_and_run_more_tests.sh generate_and_run_more_tests: Add testuninitvar 2015-07-26 11:29:02 +02:00
git-pre-commit-cppcheck git-pre-commit-cppcheck: check only added or modified source files 2016-05-07 19:09:13 +02:00
matchcompiler.py Fixed #7392 (matchcompiler fails with python 3.5) 2016-05-04 11:19:07 +02:00
parse-glibc.py PEP8 fixes. 2015-04-20 21:11:45 +03:00
readme.md PEP8 fixes. 2015-08-21 11:59:52 +03:00
reduce.cpp Fixed #7298 (reduce doesn't support --library= and --std= on the command line) 2016-01-31 12:45:17 +01:00
reduce.py reduce: try removing codeblocks below ';{}' 2016-01-28 08:05:43 +01:00
run_more_tests.sh generate_and_run_more_tests.sh: Refactoring 2015-07-22 13:44:08 +02:00
rundaca2.py rundaca: allow that start folder is set on command line, can be used when restarting daca2. 2016-02-08 09:28:02 +01:00
test_matchcompiler.py Cleanup Copyrights. Now all should be just for Cppcheck team. 2016-01-01 23:04:16 +01:00
test_showtimetop5.sh Trim tailing spaces and convert tabs to spaces. 2014-03-18 17:00:28 +02:00
testrunnerify_code.sh add small script which converts code to a format for testrunner testcases. 2015-12-17 14:25:24 +01:00
times-tags.sh PEP8 fixes. 2015-08-21 11:59:52 +03:00
times-vs.py times-vs.py: Added usage instructions 2016-01-19 13:46:21 +01:00
times.c tools/times: modified script to allow longer dataseries 2013-07-21 13:16:34 +02:00
times.sh times.sh: create a variable which can be changed to alter the iterations/how often we run cppcheck on one commit (default: 4). 2014-08-31 11:10:55 +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 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.