1--- 2# We use the clang-tidy defaults and the Google styles as a baseline, with a 3# few changes specific to VIXL: 4# -clang-analyzer-security.insecureAPI.rand: 5# This warns against the use of mrand48 (etc) and suggests replacing them 6# with arc4random. However, we are using these to drive tests and debug 7# tools, and we need the ability to manually seed the generator. This is 8# not possible with arc4random, and we do not need particularly robust 9# random numbers, so we continue to use mrand48. 10# -google-readability-todo: 11# We don't put names on TODOs. 12# -google-readability-function-size: 13# There are cases where we need (or generate) very long functions, 14# particularly involving macro-generated encoding tables and so on. 15# -google-build-using-namespace: 16# We do this in internal contexts (typically in .cc files), but clang-tidy 17# cannot tell the difference. 18# -google-explicit-constructor: 19# We follow this rule, but have some exceptions that are annotated using 20# cpplint's NOLINT format. 21# 22# TODO: The following _should_ be enabled, but currently show several failures: 23# google-readability-braces-around-statements 24# google-readability-namespace-comments 25# google-readability-casting 26# 27# TODO: Also consider enabling other rules, such as bugprone-* and cert-*. 28Checks: '-clang-analyzer-security.insecureAPI.rand,google-*,-google-readability-todo,-google-readability-function-size,-google-build-using-namespace,-google-explicit-constructor,-google-readability-braces-around-statements,-google-readability-namespace-comments,-google-readability-casting' 29HeaderFilterRegex: '\.h$' 30AnalyzeTemporaryDtors: false 31CheckOptions: 32... 33 34