llvm-project/clang
Ben Langmuir 33af4b22f8 [clang][deps] Stop sharing FileManager across module builds in scanner
Sharing the FileManager across implicit module builds currently leaks
paths looked up in an importer into the built module itself. This can
cause non-deterministic results across scans. It is especially bad for
modules since the path can be saved into the pcm file itself, leading to
stateful behaviour if the cache is shared.

This should not impact the number of real filesystem accesses in the
scanner, since it is already caching in the
DependencyScanningWorkerFilesystem.

Note: this change does not affect whether or not the FileManager is
shared across TUs in the scanner, which is a separate issue.

Differential Revision: https://reviews.llvm.org/D131412
2022-08-08 12:13:54 -07:00
..
bindings
cmake Reland "[lldb/Fuzzer] Add fuzzer for expression evaluator" 2022-08-04 11:47:06 -04:00
docs [lldb] Remove include/lldb/lldb-private.h 2022-08-08 12:03:53 -07:00
examples
include [clang] LLVM_FALLTHROUGH => [[fallthrough]]. NFC 2022-08-08 09:12:46 -07:00
lib [clang][deps] Stop sharing FileManager across module builds in scanner 2022-08-08 12:13:54 -07:00
runtime
test [clang][deps] Stop sharing FileManager across module builds in scanner 2022-08-08 12:13:54 -07:00
tools [LinkerWrapper] Use C++17 structured bindings 2022-08-08 15:07:03 -04:00
unittests [clang] Fix redirection behaviour for cached FileEntryRef 2022-08-05 12:23:38 -07:00
utils [clang] LLVM_FALLTHROUGH => [[fallthrough]]. NFC 2022-08-08 09:12:46 -07:00
www Update the C status page from the latest working draft 2022-08-08 11:30:49 -04:00
.clang-format
.clang-tidy
.gitignore
CMakeLists.txt clang/cmake: Drop use of llvm-config for LLVM install discovery 2022-08-06 16:22:59 -04:00
CODE_OWNERS.TXT
INSTALL.txt
LICENSE.TXT
ModuleInfo.txt
NOTES.txt
README.txt

//===----------------------------------------------------------------------===//
// C Language Family Front-end
//===----------------------------------------------------------------------===//

Welcome to Clang.  This is a compiler front-end for the C family of languages
(C, C++, Objective-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 web sites.  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:
  https://discourse.llvm.org/c/clang/

If you find a bug in Clang, please file it in the LLVM bug tracker:
  http://llvm.org/bugs/