Make DeprecatedOrUnsafeBufferHandling not high severity
This tidy check has been disabled by default globally, in build/soong/cc/config/tidy.go. Local projects can enable it to find/fix such issues, but if not fixed, it should not be treated as a high severity one and not to alarm daily builds. Bug: 227361697 Test: warn.py --url=http://cs/android --separator='?l=' build.log > warnings.html Test: warn.py --gencsv build.log > warnings.csv Change-Id: Ifa65a788ddc6a67ed3250d5bed737c6e3b153617
This commit is contained in:
parent
857260905b
commit
1a1f90e49a
1 changed files with 1 additions and 0 deletions
|
@ -224,6 +224,7 @@ warn_patterns = [
|
|||
analyzer_warn_check('clang-analyzer-valist.Unterminated'),
|
||||
analyzer_group_check('clang-analyzer-core.uninitialized'),
|
||||
analyzer_group_check('clang-analyzer-deadcode'),
|
||||
analyzer_warn_check('clang-analyzer-security.insecureAPI.DeprecatedOrUnsafeBufferHandling'),
|
||||
analyzer_warn_check('clang-analyzer-security.insecureAPI.bcmp'),
|
||||
analyzer_warn_check('clang-analyzer-security.insecureAPI.bcopy'),
|
||||
analyzer_warn_check('clang-analyzer-security.insecureAPI.bzero'),
|
||||
|
|
Loading…
Reference in a new issue