llvm-project/clang
Richard Smith a560ccf2af Switch to a different workaround for unimplementability of P0145R3 in MS ABIs.
Instead of ignoring the evaluation order rule, ignore the "destroy parameters
in reverse construction order" rule for the small number of problematic cases.
This only causes incorrect behavior in the rare case where both parameters to
an overloaded operator <<, >>, ->*, &&, ||, or comma are of class type with
non-trivial destructor, and the program is depending on those parameters being
destroyed in reverse construction order.

We could do a little better here by reversing the order of parameter
destruction for those functions (and reversing the argument evaluation order
for all direct calls, not just those with operator syntax), but that is not a
complete solution to the problem, as the same situation can be reached by an
indirect function call.

Approach reviewed off-line by rnk.

llvm-svn: 282777
2016-09-29 21:30:12 +00:00
..
INPUTS
bindings bindings: expose diagnostic formatting to Python 2016-08-11 05:31:07 +00:00
cmake [CMake] Adding toolchain targets to PGO and Apple CMake caches 2016-08-17 21:51:38 +00:00
docs [sanitizer-coverage] a bit more docs 2016-09-29 19:06:09 +00:00
examples Reapply r276973 "Adjust Registry interface to not require plugins to export a registry" 2016-08-05 11:01:08 +00:00
include P0127R2: Support type deduction for types of non-type template parameters in 2016-09-28 23:55:27 +00:00
lib Switch to a different workaround for unimplementability of P0145R3 in MS ABIs. 2016-09-29 21:30:12 +00:00
runtime [CMake] Properly connecting Compiler-RT check and test-depends 2016-09-01 18:28:49 +00:00
test Switch to a different workaround for unimplementability of P0145R3 in MS ABIs. 2016-09-29 21:30:12 +00:00
tools [analyzer][scan-build-py] subprocess output handling reviewed in clang module 2016-09-24 00:20:59 +00:00
unittests Merge conflicting replacements when they are order-independent. 2016-09-28 11:02:16 +00:00
utils Fix warnings in clang-completion-mode.el. 2016-09-28 10:20:10 +00:00
www Switch to a different workaround for unimplementability of P0145R3 in MS ABIs. 2016-09-29 21:30:12 +00:00
.arcconfig Upgrade all the .arcconfigs to https. 2016-07-14 13:15:37 +00:00
.clang-format
.clang-tidy Try to use readability-identifier-naming check on Clang. 2016-04-13 08:59:49 +00:00
.gitignore
CMakeLists.txt [CMake] More robust handling for bootstrap variables 2016-09-22 00:18:12 +00:00
CODE_OWNERS.TXT
INSTALL.txt
LICENSE.TXT Update copyright year to 2016. 2016-03-30 22:38:44 +00:00
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/