aboutsummaryrefslogtreecommitdiff
path: root/clang/lib/Basic/Module.cpp
diff options
context:
space:
mode:
authorTom Honermann <tom.honermann@intel.com>2022-04-01 18:52:29 -0700
committerTom Honermann <tom@honermann.net>2022-04-05 15:34:35 -0400
commitc54ad1360248e28a436a6a6c560ba5952d8e98cb (patch)
tree30fc3f327970a17f2f90eeeffc3b5658066d0c47 /clang/lib/Basic/Module.cpp
parent019e7b7f6ed259296d04d9bc1550ea2898f48ec7 (diff)
downloadllvm-c54ad1360248e28a436a6a6c560ba5952d8e98cb.zip
llvm-c54ad1360248e28a436a6a6c560ba5952d8e98cb.tar.gz
llvm-c54ad1360248e28a436a6a6c560ba5952d8e98cb.tar.bz2
[Lint][Verifier] NFC: Rename 'Assert*' macros to 'Check*'.
The LLVM IR verifier and analysis linter defines and uses several macros in code that performs validation of IR expectations. Previously, these macros were named with an 'Assert' prefix. These names were misleading since the macro definitions are not conditioned on build kind; they are defined identically in builds that have asserts enabled and those that do not. This was confusing since an LLVM developer might expect these macros to be conditionally enabled as 'assert' is. Further confusion was possible since the LLVM IR verifier is implicitly disabled (in Clang::ConstructJob()) for builds without asserts enabled, but only for Clang driver invocations; not for clang -cc1 invocations. This could make it appear that the macros were not active for builds without asserts enabled, e.g. when investigating behavior using the Clang driver, and thus lead to surprises when running tests that exercise the clang -cc1 interface. This change renames this set of macros as follows: Assert -> Check AssertDI -> CheckDI AssertTBAA -> CheckTBAA
Diffstat (limited to 'clang/lib/Basic/Module.cpp')
0 files changed, 0 insertions, 0 deletions