From 138e06fec7ac045a17ab664ec533c3a9fd123b23 Mon Sep 17 00:00:00 2001 From: "Matthias J. Kannwischer" Date: Tue, 15 Oct 2019 14:22:39 +0200 Subject: [PATCH] ignore new clang warning security.insecureAPI.DeprecatedOrUnsafeBufferHandling clang9.0.0 (https://releases.llvm.org/9.0.0/tools/clang/docs/ReleaseNotes.html) adds a new satic analyzer: security.insecureAPI.DeprecatedOrUnsafeBufferHandling which throws warnings if you use "unsafe" buffer handling functions which includes memset and memcpy. We have memset and mempy all over the place, so I think it's best to ignore this warning. All the occurences that I looked at seemed perfectly "safe" to me. --- .clang-tidy | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.clang-tidy b/.clang-tidy index 5189c670..cbfca735 100644 --- a/.clang-tidy +++ b/.clang-tidy @@ -1,5 +1,5 @@ --- -Checks: '*,-llvm-header-guard,-hicpp-*,-readability-function-size,-google-readability-todo,-readability-magic-numbers,-cppcoreguidelines-avoid-magic-numbers,-readability-isolate-declaration,-readability-uppercase-literal-suffix' +Checks: '*,-llvm-header-guard,-hicpp-*,-readability-function-size,-google-readability-todo,-readability-magic-numbers,-cppcoreguidelines-avoid-magic-numbers,-readability-isolate-declaration,-readability-uppercase-literal-suffix,-clang-analyzer-security.insecureAPI.DeprecatedOrUnsafeBufferHandling' WarningsAsErrors: '*' HeaderFilterRegex: '.*' AnalyzeTemporaryDtors: false