llvm-project/clang
Richard Smith 8f8b9f2cca PR47805: Use a single object for a function parameter in the caller and
callee in constant evaluation.

We previously made a deep copy of function parameters of class type when
passing them, resulting in the destructor for the parameter applying to
the original argument value, ignoring any modifications made in the
function body. This also meant that the 'this' pointer of the function
parameter could be observed changing between the caller and the callee.

This change completely reimplements how we model function parameters
during constant evaluation. We now model them roughly as if they were
variables living in the caller, albeit with an artificially reduced
scope that covers only the duration of the function call, instead of
modeling them as temporaries in the caller that we partially "reparent"
into the callee at the point of the call. This brings some minor
diagnostic improvements, as well as significantly reduced stack usage
during constant evaluation.
2020-10-13 18:50:46 -07:00
..
INPUTS
bindings [python][tests] Fix string comparison with "is" 2020-09-28 21:11:50 +02:00
cmake Update documentation and implementation of stage3 build 2020-10-08 07:55:37 +02:00
docs AMDGPU: Remove -mamdgpu-debugger-abi option 2020-10-13 12:20:28 -04:00
examples [cmake] Fix build of attribute plugin example on Windows 2020-09-07 10:04:32 +02:00
include Basic: Simplify SourceManager::getBuffer overload, NFC 2020-10-13 17:52:59 -04:00
lib PR47805: Use a single object for a function parameter in the caller and 2020-10-13 18:50:46 -07:00
runtime [CMake][compiler-rt][libunwind] Compile assembly files as ASM not C, unify workarounds 2020-08-27 15:40:15 +03:00
test PR47805: Use a single object for a function parameter in the caller and 2020-10-13 18:50:46 -07:00
tools [MinGW][clang-shlib] Build only when LLVM_LINK_LLVM_DYLIB is enabled 2020-10-12 23:28:23 +03:00
unittests Revert "DirectoryWatcher: add an implementation for Windows" 2020-10-13 12:35:22 -07:00
utils Revert "Recommit "[CUDA][HIP] Defer overloading resolution diagnostics for host device functions"" 2020-09-24 11:16:54 -07:00
www [c++17] Implement P0145R3 during constant evaluation. 2020-10-06 12:30:26 -07:00
.clang-format
.clang-tidy
.gitignore
CMakeLists.txt [OpenMP] Change CMake Configuration to Build for Highest CUDA Architecture by Default 2020-10-08 12:09:34 -04:00
CODE_OWNERS.TXT
INSTALL.txt
LICENSE.TXT
ModuleInfo.txt
NOTES.txt
README.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 development mailing list:
  http://lists.llvm.org/mailman/listinfo/cfe-dev

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