From: Ferruh Yigit <ferruh.yigit@intel.com>
To: dev@dpdk.org
Cc: Ferruh Yigit <ferruh.yigit@intel.com>
Subject: [dpdk-dev] [PATCH] devtools: add cppcheck wrapper
Date: Thu, 11 Feb 2021 17:27:58 +0000 [thread overview]
Message-ID: <20210211172758.2977369-1-ferruh.yigit@intel.com> (raw)
Adding wrapper script for cppcheck code analysis tool.
usage: cppcheck.sh [-h] [path]
Without any argument current folder scanned with all sub folders, if
'path' argument provided, that 'path' is scanned with all its
subfolders, like:
"./devtools/cppcheck.sh lib/librte_ethdev/"
The output log is saved to 'cppcheck_error.txt' in current folder.
Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
---
devtools/cppcheck.sh | 67 ++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 67 insertions(+)
create mode 100755 devtools/cppcheck.sh
diff --git a/devtools/cppcheck.sh b/devtools/cppcheck.sh
new file mode 100755
index 000000000000..935eb5d9d625
--- /dev/null
+++ b/devtools/cppcheck.sh
@@ -0,0 +1,67 @@
+#! /bin/sh
+# SPDX-License-Identifier: BSD-3-Clause
+# Copyright(c) 2021 Intel Corporation
+
+# wrapper script for cppcheck code analysis tool
+# Args:
+# $1: path to scan (optional)
+
+CPPCHECK_BIN=cppcheck
+out=cppcheck_error.txt
+
+which ${CPPCHECK_BIN} > /dev/null 2> /dev/null
+if [ $? -ne 0 ]; then
+ echo "${CPPCHECK_BIN} is missing!"
+ exit 1
+fi
+
+print_usage () {
+ cat <<- END_OF_HELP
+ usage: $(basename $0) [-h] [path]
+
+ Wrapper on checkpatch tool. Output goes to ${out} file.
+
+ Without parameter current folder with all subfolders scanned. It is possible
+ to provide a sub-folder to recude the scan to that folder.
+ END_OF_HELP
+}
+
+if [ "$1" = "-h" ]; then
+ print_usage
+ exit 1;
+fi
+
+dir=${1:-$(dirname $(readlink -f $0))/..}
+if [ ! -e ${dir} ]; then
+ echo "\"${dir}\" is not valid folder/file to check"
+ exit 1
+fi
+
+
+suppress_args="
+ --suppress=invalidPrintfArgType_sint \
+ --suppress=invalidPrintfArgType_uint \
+ --suppress=duplicateAssignExpression \
+ --suppress=nullPointerRedundantCheck \
+ --suppress=identicalConditionAfterEarlyExit \
+ --suppress=objectIndex
+ "
+
+# all, warning, performance, portability,
+# information, unusedFunction, missingInclude
+additional_checks=warning
+
+${CPPCHECK_BIN} \
+ -j64 \
+ --language=c \
+ --enable=${additional_checks} \
+ --force \
+ ${suppress_args} \
+ ${dir} \
+ 2> ${out}
+
+if [ $? -eq 0 ]; then
+ echo -e "\nOutput saved to ${out}"
+else
+ exit $?
+fi
--
2.29.2
next reply other threads:[~2021-02-11 17:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-11 17:27 Ferruh Yigit [this message]
2021-05-20 7:48 ` Thomas Monjalon
2023-06-12 23:55 ` Stephen Hemminger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210211172758.2977369-1-ferruh.yigit@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).