forked from bitcoin-core/secp256k1
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add simple static checker based on clang-query
This add a simple static checker based on clang-query, which is a tool that could be described as a "clever grep" for abstract syntax trees (ASTs). As an initial proof of usefulness, this commit adds these checks: - No uses of floating point types. - No use of certain reserved identifiers (e.g., "mem(...)", bitcoin-core#829). - No use of memcmp (bitcoin-core#823). The checks are easily extensible. The main purpose is to run the checker on CI, and this commit adds the checker to the Travis CI script. This currently requires clang-query version at least 10. (However, it's not required not compile with clang version 10, or with clang at all. Just the compiler flags must be compatible with clang.) Clang-query simply uses the clang compiler as a backend for generating the AST. In order to determine the compile in which the code is supposed to be compiled (e.g., compiler flags such as -D defines and include paths), it reads a compilation database in JSON format. There are multiple ways to generate this database. The easiest way to obtain such a database is to use a tool that intercepts the make process and build the database. On Travis CI, we currently use "bear" for this purpose. It's a natural choice because there is an Ubuntu package for it. If you want to run this locally, bear is a good choice but other tools such as compiledb (Python) are available.
- Loading branch information
1 parent
c6b6b8f
commit 0114113
Showing
4 changed files
with
81 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,53 @@ | ||
#!/bin/sh | ||
|
||
set -u | ||
|
||
matcher=$(cat <<'EOF' | ||
set print-matcher true | ||
enable output detailed-ast | ||
### Expressions of any floating point type (unless in a system header) | ||
match expr(allOf(unless(isExpansionInSystemHeader()), hasType(realFloatingPointType()))) | ||
### Calls to memcmp (secp256k1_memcmp_var should be used instead) | ||
match callExpr(callee(functionDecl(hasName("memcmp")))) | ||
### Reserved identifiers (unless in a system header) with external linkage or at file scope. | ||
# Any function is in file scope. Any variable with static storage (unless static local variable) is in file scope. | ||
# Allowed exceptions: __builtin_expect | ||
# We need the "::" due to LLVM bug 47879. | ||
match namedDecl(allOf(unless(isExpansionInSystemHeader()), anyOf(hasExternalFormalLinkage(), functionDecl(), varDecl(allOf(hasStaticStorageDuration(), unless(isStaticLocal())))), allOf(matchesName("^::(_|((mem|is|to|str|wcs)[a-z]))"), unless(hasAnyName("__builtin_expect"))))) | ||
### Reserved type names (unless in a system header) | ||
# Allowed exceptions: uint128_t, int128_t, __int128_t, __uint128_t (the latter two are "implicit", i.e., added by the compiler) | ||
match typedefDecl(allOf(unless(isExpansionInSystemHeader()), matchesName("(^::u?int)|(_t$)"), unless(hasAnyName("int128_t", "uint128_t", "__int128_t", "__uint128_t")))) | ||
quit | ||
EOF | ||
) | ||
|
||
# Poor man's JSON parser. | ||
# This is not great but it works with the output of all common tools and it does not need extra dependencies. | ||
files=$(grep 'file' compile_commands.json | uniq | cut -d '"' -f 4) | ||
echo "Running clang-query on files:" | ||
echo "$files" | ||
|
||
output=$(echo "$matcher" | ${CLANG_QUERY:-clang-query} "$@" $files) | ||
status=$? | ||
if [ $status -ne 0 ] | ||
then | ||
exit $status | ||
fi | ||
|
||
echo "$output" | ||
# For some reason, clang-query returns a zero status even if clang failed to process the file (LLVM Bug 47880). | ||
# This is not a big issue. If clang errors, we'll notice that when trying to compile with clang anyway. | ||
# We still try to catch this case by grepping also for "error:". | ||
echo "$output" | grep -qE "^Match #|error:" | ||
if [ $? -eq 0 ] | ||
then | ||
exit 1 | ||
fi | ||
|
||
echo | ||
exit 0 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters