Changes

[Attributor] Deduce memory behavior of functions and arguments
Deduce the memory behavior, aka "read-none", "read-only", or
"write-only", for functions and arguments.
Reviewers: sstefan1, uenoku
Subscribers: hiraditya, bollu, jfb, llvm-commits
Tags: #llvm
Differential Revision: https://reviews.llvm.org/D67384
llvm-svn: 373965

[llvm-lipo] Relax the check of the specified input file architecture
cctools lipo only compares the cputypes when it verifies that the
specified (via -arch) input file and the architecture match. This diff
adjusts the behavior of llvm-lipo accordingly. 
Differential revision: https://reviews.llvm.org/D68319
Test plan: make check-all
llvm-svn: 373966

[WebAssembly] Add memory intrinsics handling to mayThrow()
Summary: Previously, `WebAssembly::mayThrow()` assumed all inputs are
global addresses. But when intrinsics, such as `memcpy`, `memmove`, or
`memset` are lowered to external symbols in instruction selection and
later emitted as library calls. And these functions don't throw.
This patch adds handling to those memory intrinsics to `mayThrow` 
function. But while most of libcalls don't throw, we can't guarantee all 
of them don't throw, so currently we conservatively return true for all 
other external symbols.
I think a better way to solve this problem is to embed 'nounwind' info 
in `TargetLowering::CallLoweringInfo`, so that we can access the info 
from the backend. This will also enable transferring 'nounwind' 
properties of LLVM IR instructions. Currently we don't transfer that 
info and we can only access properties of callee functions, if the 
callees are within the module. Other targets don't need this info in the 
backend because they do all the processing before isel, but it will help 
us because that info will reduce code size increase in fixing unwind 
destination mismatches in CFGStackify.
But for now we return false for these memory intrinsics and true for all 
other libcalls conservatively.
Reviewers: dschuff
Subscribers: sbc100, jgravelle-google, hiraditya, sunfish, llvm-commits
Tags: #llvm
Differential Revision: https://reviews.llvm.org/D68553
llvm-svn: 373967

Mark constructor as default and remove implementation (NFC)
llvm-svn: 373968

[llvm-c] Add UnaryOperator to LLVM_FOR_EACH_VALUE_SUBCLASS macro
Note that we are not sure where the tests for these functions lives.
This was discussed in the Phab Diff.
Differential Revision: https://reviews.llvm.org/D68588
llvm-svn: 373969

[CMake] We only want to copy the headers for macOS.
<rdar://problem/55916729>
llvm-svn: 373970

    [libc++] Remove C++03 variadics in shared_ptr (v2)
    Summary: In my last patch (D67675) I forgot a few variadics. This
patch removes the remaining make_shared and allocate_shared C++03
variadics.
    Reviewers: ldionne, EricWF, mclow.lists
    Subscribers: christof, dexonsmith, libcxx-commits
    Tags: #libc
    Differential Revision: https://reviews.llvm.org/D68000
llvm-svn: 373971

[Attributor][FIX] Remove assertion wrong for on invalid IRPositions
llvm-svn: 373972

[Diagnostics] Emit better -Wbool-operation's warning message if we known
that the result is always true
llvm-svn: 373973

[llvm-lipo] Add TextAPI to LINK_COMPONENTS
Summary: D68319 uses `MachO::getCPUTypeFromArchitecture` and without
this builds with `-DBUILD_SHARED_LIBS=ON` fail.
Reviewers: alexshap
Subscribers: mgorny, llvm-commits
Tags: #llvm
Differential Revision: https://reviews.llvm.org/D68594
llvm-svn: 373974

[WebAssembly] Fix unwind mismatch stat computation
Summary: There was a bug when computing the number of unwind destination 
mismatches in CFGStackify. When there are many mismatched calls that 
share the same (original) destination BB, they have to be counted 
separately.
This also fixes a typo and runs `fixUnwindMismatches` only when the wasm 
exception handling is enabled. This is to prevent unnecessary 
computations and does not change behavior.
Reviewers: dschuff
Subscribers: sbc100, jgravelle-google, hiraditya, sunfish, llvm-commits
Tags: #llvm
Differential Revision: https://reviews.llvm.org/D68552
llvm-svn: 373975