
Created new module bugprone and placed the check in that. Finds memset() calls with potential mistakes in their arguments. Replaces and extends the existing google-runtime-memset-zero-length check. Cases covered: * Fill value is a character '0'. Integer 0 might have been intended. * Fill value is out of char range and gets truncated. * Byte count is zero. Potentially swapped with the fill value argument. Patch by: Reka Nikolett Kovacs Differential Revision: https://reviews.llvm.org/D32700 llvm-svn: 308020
39 lines
1.2 KiB
C++
39 lines
1.2 KiB
C++
//===--- BugproneTidyModule.cpp - clang-tidy ------------------------------===//
|
|
//
|
|
// The LLVM Compiler Infrastructure
|
|
//
|
|
// This file is distributed under the University of Illinois Open Source
|
|
// License. See LICENSE.TXT for details.
|
|
//
|
|
//===----------------------------------------------------------------------===//
|
|
|
|
#include "../ClangTidy.h"
|
|
#include "../ClangTidyModule.h"
|
|
#include "../ClangTidyModuleRegistry.h"
|
|
#include "SuspiciousMemsetUsageCheck.h"
|
|
|
|
namespace clang {
|
|
namespace tidy {
|
|
namespace bugprone {
|
|
|
|
class BugproneModule : public ClangTidyModule {
|
|
public:
|
|
void addCheckFactories(ClangTidyCheckFactories &CheckFactories) override {
|
|
CheckFactories.registerCheck<SuspiciousMemsetUsageCheck>(
|
|
"bugprone-suspicious-memset-usage");
|
|
}
|
|
};
|
|
|
|
} // namespace bugprone
|
|
|
|
// Register the BugproneTidyModule using this statically initialized variable.
|
|
static ClangTidyModuleRegistry::Add<bugprone::BugproneModule>
|
|
X("bugprone-module", "Adds checks for bugprone code constructs.");
|
|
|
|
// This anchor is used to force the linker to link in the generated object file
|
|
// and thus register the BugproneModule.
|
|
volatile int BugproneModuleAnchorSource = 0;
|
|
|
|
} // namespace tidy
|
|
} // namespace clang
|