If we're using the pure non-fragile ABI, then skip some of the contortions required to support the transitional ABI.

llvm-svn: 134612

Set a flag to tell the runtime when we're compiling in ARC mode and use the pure-nonfragile ABI for both ARC and GC mode.

llvm-svn: 134611

where we have an immediate need of a retained value.

As an exception, don't do this when the call is made as the immediate
operand of a __bridge retain.  This is more in the way of a workaround
than an actual guarantee, so it's acceptable to be brittle here.

rdar://problem/9504800

llvm-svn: 134605

llvm-svn: 134589

llvm-svn: 134536

exception in Objective-C;  in Objective-C++ we still use std::terminate().
This is only available in very recent runtimes.

llvm-svn: 134456

structure to hold inferred information, then propagate each invididual
bit down to -cc1.  Separate the bits of "supports weak" and "has a native
ARC runtime";  make the latter a CodeGenOption.

The tool chain is still driving this decision, because it's the place that
has the required deployment target information on Darwin, but at least it's
better-factored now.

llvm-svn: 134453

hardwired into the default pass list.

llvm-svn: 134445

The start of some work on getting -mno-mmx working the way we want it to.

llvm-svn: 134300

Fixes rdar://9714064

llvm-svn: 134292

initializer. Previously, we only used guard variables for weak static
data members. Fixes <rdar://problem/9692249>.

llvm-svn: 134266

trivial default constructors. This generated-code regression was
caused by r131796, which had simplified the handling of default
initialization in Sema. Fixes <rdar://problem/9694300>.

llvm-svn: 134260

llvm-svn: 134140

llvm-svn: 134128

accessibility of an initializer which is a compound 
statement. // rdar://9694706

llvm-svn: 134091

replacing -freset-local-blocks. // rdar://9227352

llvm-svn: 134082

llvm-svn: 134065

We don't pass classes with a copy-constructor or destructor byval, so the address takes up an integer register (if one is available).  Make sure the x86-64 ABI implementation takes that into account properly.

The fixed implementation is compatible with the implementation both gcc and llvm-gcc use.

rdar://9686430 . (This is the issue that was reported in the thread "[LLVMdev] Segfault calling LLVM libs from a clang-compiled executable".)

llvm-svn: 134059

llvm-svn: 134050

wipe out stack blocks when they go out of scope.
// rdar://9227352

llvm-svn: 134045

Fixes rdar://9281377

llvm-svn: 134016

a vector for collection. Use iterators where needed instead.
// rdar://6817577

llvm-svn: 134015

llvm-svn: 133943

llvm-svn: 133931

llvm-svn: 133864

llvm-svn: 133861

by removing the redundant type parameter.

llvm-svn: 133860

arithmetic on a VLA as 'nsw', per discussion with djg, and
implement pointer arithmetic (other than array accesses) and
pointer subtraction for VLA types.

llvm-svn: 133855

in the variable to an inline asm which gets run when the variable
goes out of scope.

llvm-svn: 133840

Sorry, this was a bad idea.  Within clang these builtins are in a separate
"ARM" namespace, but the actual builtin names should clearly distinguish tha
they are target specific.

llvm-svn: 133833

llvm-svn: 133829

not sizes;  so that we use well-typed allocas;  and so that we
properly recurse through the full set of variably-modified types.

llvm-svn: 133827

llvm-svn: 133826

in fragile abi mode and some other cleanups. // rdar://8940528

llvm-svn: 133747

in Darwin's fragile abi mode.  // rdar://8940528

llvm-svn: 133639

llvm-svn: 133623

objects, so that we steal the retain count of a temporary __strong
pointer (zeroing out that temporary), eliding a retain/release
pair. Addresses <rdar://problem/9364932>.

llvm-svn: 133621

retain/release the temporary object appropriately. Previously, we
would only perform the retain/release operations when the reference
would extend the lifetime of the temporary, but this does the wrong
thing across calls.

llvm-svn: 133620

that takes an ArrayRef.

llvm-svn: 133615

existence by always threading an edge from the catchall.  Not doing
this was previously causing a crash in the very extreme case where
neither the normal cleanup nor the EH catchall was actually reachable:
we would delete the catchall entry block, which would cause us to
delete the entry block of the finally cleanup as well because the
cleanup logic would merge the blocks, which in turn triggered an assert
because later blocks in the finally would still be using values from the
entry.  Laziness turns out to be the most elegant solution to the problem.

llvm-svn: 133601