[analyzer] Match standard libraries regardless `restrict` qualifier Remove the `restrict` sensitivity from StdLibraryFunctionsChecker to simplify the code and remove the risk of a failure to match. c5dd283d2f2409dfca13628e15bbf0e526dfc3f0 demonstrates that UCRT does not specify the `restrict` qualifiers leading to non-matches in StdLibraryFunctionsChecker. There might be other non-standard-compliant libc implementations that share this drawback. The `restrict` sensitivity does not seem to improve analyzer precision in any practical case, yet it increases code complexity and adds a risk of FNs as happened with UCRT. -- CPP-9480 GitOrigin-RevId: 59edc10bd0b2aeb43a6d4025874c1986f75c7973
Welcome to Clang.
This is a compiler front-end for the C family of languages (C, C++ and Objective-C) which is built as part of the LLVM compiler infrastructure project.
Unlike many other compiler frontends, Clang is useful for a number of things beyond just compiling code: we intend for Clang to be host to a number of different source-level tools. One example of this is the Clang Static Analyzer.
If you're interested in more (including how to build Clang) it is best to read the relevant websites. Here are some pointers:
Information on Clang: http://clang.llvm.org/
Building and using Clang: http://clang.llvm.org/get_started.html
Clang Static Analyzer: http://clang-analyzer.llvm.org/
Information on the LLVM project: http://llvm.org/
If you have questions or comments about Clang, a great place to discuss them is on the Clang forums:
If you find a bug in Clang, please file it in the LLVM bug tracker: