Avoid applying retain/release effects twice in RetainCountChecker when a function call was inlined (i.e., we do not need to apply summaries in such cases).

llvm-svn: 153309

llvm-svn: 153308

class template's definition, and for explicit specializations of such enum
members.

llvm-svn: 153304

return from clang_getCursorLocation the start location of the method name.

rdar://11105223

llvm-svn: 153303

llvm-svn: 153302

during construction of branches for chained logical operators.

This makes -fsyntax-only for test/Sema/many-logical-ops.c about 32x times faster.

With measuring SemaExpr.cpp I see differences below the noise level.

llvm-svn: 153297

llvm-svn: 153295

declared at file scope.
// rdar://11006566

llvm-svn: 153293

llvm-svn: 153292

llvm-svn: 153291

cast the value to x86_mmx. This gives the ASM string the correct call signature.
<rdar://problem/10919182>

llvm-svn: 153290

llvm-svn: 153289

Make sure we correctly set the alignment for vector loads and stores associated with vector element lvalues.  Patch by Kevin Schoedel (with some minor modifications by me).

llvm-svn: 153285

llvm-svn: 153283

llvm-svn: 153281

llvm-svn: 153280

(Stats Checker).

llvm-svn: 153279

at global scope properly, issue diagnostics.

llvm-svn: 153271

llvm-svn: 153264

property attributes. // rdar://11095151

llvm-svn: 153261

make sure to fully load its external lexical and visible declarations before
re-writing it.

rdar://10914192

llvm-svn: 153254

llvm-svn: 153246

"Teach" RetainCountChecker about dispatch_set_context, which can indirectly free its argument later.  Fixes <rdar://problem/11059275>.

llvm-svn: 153244

relied on an artifact of how the inliner and subsequent passes in
clang's -O3 mode happen to treat basic blocks and the labels for the
basic blocks. In my work on the inliner, and changed this fundamental
assumption, and the label that was being checked on the entry basic
block will no longer appear in opt builds. There was no reason to expect
the label to always be present anyways, much to my regret.

I've changed the test to just ensure that we return an immediate
constant. If there are intervening instructions, that's bad, but not
really that relevant to the test.

I'd love it if others have a better way of checking that a function body
contains only a 'ret' instruction that isn't dependent on whether or not
the entry block receives a label...

llvm-svn: 153243

Fix broken CFG when an initializer is a statement expression that starts with a while loop (PR 12325).

llvm-svn: 153242

specialization is known to be incomplete. If we're asked to try to
complete it, don't attempt to instantiate it again -- that can lead
to stack overflow, and to rejects-valids if the class being incomplete
is not an error.

llvm-svn: 153236

evaluate RHS if LHS could not be evaluated and keepEvaluatingAfterFailure() is false.

llvm-svn: 153235

llvm-svn: 153232

all objc_msgSend unctions to void parameters and void return.
// rdar://11094890

llvm-svn: 153227

non-constant value encountered.  This allows the evaluator to deduce that
expressions like (x < 5 || true) is equal to true.  Previously, it would visit
x and determined that the entire expression is could not evaluated to a
constant.

This fixes PR12318.

llvm-svn: 153226

llvm-svn: 153220

the diagnostic instead of displaying ''.
// rdar://11082110

llvm-svn: 153219

llvm-svn: 153217

rdar://11054144

llvm-svn: 153216

llvm-svn: 153214

Specifically, we use the last store of the leaked symbol in the leak diagnostic.
(No support for struct fields since the malloc checker doesn't track those
yet.)

+ Infrastructure to track the regions used in store evaluations.
This approach is more precise than iterating the store to
obtain the region bound to the symbol, which is used in RetainCount
checker. The region corresponds to what is uttered in the code in the
last store and we do not rely on the store implementation to support
this functionality.

llvm-svn: 153212

So that others could use it as well. No functionality change.

llvm-svn: 153211

(The fix was committed in r152982.)

llvm-svn: 153210

The getARMTargetCPU and getLLVMArchSuffixForARM functions exist in both
Toolchain.cpp and Tools.cpp.  This stuff needs a thorough overhaul.  In the
meantime, this patch at least makes them consistent.  One version had been
converted to use StringSwitch, and the other version had new Cortex M-series
processors added.

llvm-svn: 153202

c-mode to match behavior with void functions in c. Issue
warning with -pedantic. // rdar://11069896

llvm-svn: 153200