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

llvm-svn: 133619

to, including cv-qualifications.

llvm-svn: 133618

llvm-svn: 133617

llvm-svn: 133616

that takes an ArrayRef.

llvm-svn: 133615

llvm-svn: 133614

llvm-svn: 133613

llvm-svn: 133612

representing a constant reference to ValType. Normally this is just
"const ValType &", but when ValType is a std::vector we want to use
ArrayRef as the reference type.

llvm-svn: 133611

lifetime is well-known and restricted, cleaning them up manually is easy to miss and cause a leak.

Use it to plug the leaking of TemplateIdAnnotation objects. rdar://9634138.

llvm-svn: 133610

test/lit.site.cfg, not Unit/test/lit.site.cfg.

llvm-svn: 133609

test/lit.site.cfg, not Unit/test/lit.site.cfg.

llvm-svn: 133608

be one with only one unconditional branch and no phis. Duplicating the phis in this case
is possible, but requeres liveness analysis or breaking edges.

llvm-svn: 133607

llvm-svn: 133605

llvm-svn: 133604

where the environment variables for log files (DEBUG_LLDB_LOG and DEBUG_GDB_REMOTE_LOG)
are not defined.

llvm-svn: 133603

a valid SB API object.  Modify the test case to accommodate.

llvm-svn: 133602

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

FunctionTemplateDecl. I'm not quite sure what else it could be, though,
and would appreciate some insight.

This ought to fix the broken builds

llvm-svn: 133600

llvm-svn: 133599

process entry point.

llvm-svn: 133598

contained the current line marker. This is now an option which is not enabled
for the API disassembly call.

llvm-svn: 133597

probably shouldn't cover the implicit member case, but it needs to until
more descriptive diagnostics are implemented.

llvm-svn: 133594

are also present.

llvm-svn: 133593

respect that when deciding whether -objc-exceptions implies the
-fexceptions -cc1 option.

llvm-svn: 133590

Patch by Wei-Ren Chen

llvm-svn: 133589

llvm-svn: 133585

lookup. Previously, it was breaking self-host, but it's been a week and
a half and I can't reproduce, so I need to see if it's still failing.

llvm-svn: 133581

Fix PR10168: don't warn for unused non-dependent variables in both the template definition and each instantiation.

llvm-svn: 133580

llvm-svn: 133577

llvm-svn: 133574

First part of PR9968: the __range variable in a dependent C++11 for-range statement is implicitly used by that statement.

llvm-svn: 133572

llvm-svn: 133571

operators. There is a consistent design of having the "silence the
warning" option first.

llvm-svn: 133570

llvm-svn: 133569

TableGen had diagnostic printers sprinkled about in a few places. Pull them
together into a single location in Error.cpp.

llvm-svn: 133568

llvm-svn: 133567

to emit "movd" across the board to continue supporting a Darwin assembler bug.
This is the reincarnation of r133452.

llvm-svn: 133565

not "test_long_long_type_with_dsym".

llvm-svn: 133562