cppcheck/tools
Daniel Marjamäki 56a5b0d55f daca2: If cppcheck crash, the exitcode is nonzero. Write message in the report when the exitcode is nonzero. 2013-12-31 18:24:32 +01:00
..
argparse.py autopep8 formatting 2013-10-18 17:35:59 +02:00
aws.py ci.py: copy std.cfg to daca2 folder to get better results. 2013-12-12 20:10:46 +01:00
ci.py ci: use CFGDIR flag 2013-12-28 12:17:30 +01:00
daca2-report.py daca2-report: insert spaces between 'Most recently updated' items 2013-12-15 12:33:06 +01:00
daca2.py daca2: If cppcheck crash, the exitcode is nonzero. Write message in the report when the exitcode is nonzero. 2013-12-31 18:24:32 +01:00
dmake.cpp dmake: Improved handling of CFGDIR 2013-12-28 12:15:08 +01:00
dmake.vcproj Tools: Update VS project file. 2011-08-11 23:40:10 +03:00
extracttests.py autopep8 formatting 2013-10-18 17:35:59 +02:00
matchcompiler.py matchcompiler: autopep8 formatting 2013-10-13 11:01:50 +02:00
readme.md Add readme.md for 'tools' directory 2013-12-27 13:58:08 -02:00
reduce.cpp reduce: Fixed compiler error (MathLib::longToString() doesnt exist) 2013-10-06 19:07:47 +02:00
test_matchcompiler.py autopep8 formatting 2013-10-18 17:35:59 +02:00
times-tags.sh times: added shell script that executes previous tags 2012-11-30 12:12:04 +01:00
times.c tools/times: modified script to allow longer dataseries 2013-07-21 13:16:34 +02:00
times.sh tools/times: minor tweaks 2012-11-27 12:20:23 +01:00
tools.pro Add general PRO file for console builds. 2012-06-18 09:28:32 +03: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 intented 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.