llvm-svn: 162722

llvm-svn: 162721

This helper function (in the clang::ento::bugreporter namespace) may add more
than one visitor, but conceptually it's tracking a single use of a null or
undefined value and should do so as best it can.

Also, the BugReport parameter has been made a reference to underscore that
it is non-optional.

llvm-svn: 162720

As Anna pointed out to me offline, it's a little silly to walk backwards through
the graph to find the store site when BugReporter will do the exact same walk
as part of path diagnostic generation.

llvm-svn: 162719

Previously, if we were tracking stores to a variable 'x', and came across this:

x = foo();

...we would simply emit a note here and stop. Now, we'll step into 'foo' and
continue tracking the returned value from there.

<rdar://problem/12114689>

llvm-svn: 162718

The two callers are using this in order to be conservative, so let's just
clarify the information that's actually being provided here. This is not
related to inlining decisions in any way.

No functionality change.

llvm-svn: 162717

with FIXMEs for unimplemented features.  No functional change intended.

llvm-svn: 162716

if we have something like:

   @synthesize prop = _prop;

and '_prop' is not declared, we will encounter a '_prop' ivar before
encountering the 'prop' synthesize declaration and we will think that
we passed the region-of-interest, missing the cursor for 'prop'.

rdar://12172700

llvm-svn: 162715

llvm-svn: 162714

It is not safe to use normal LDR instructions because they may be
reordered by the scheduler. The ATOMIC_LDR pseudos have a mayStore flag
that prevents reordering.

Atomic loads are also prevented from participating in rematerialization
and load folding.

llvm-svn: 162713

More work towards unifying asm stmt codegen.

llvm-svn: 162712

llvm-svn: 162711

change intended.

llvm-svn: 162710

llvm-svn: 162707

Fix compile error when building with C++11 - clang thinks that PRIx64 is a user-defined suffix or something

llvm-svn: 162704

<rdar://problem/12183003>

llvm-svn: 162703

Suggested by Roman Divacky.

llvm-svn: 162702

This avoids emitting many dead GEPs for large zero-initialized arrays.

llvm-svn: 162701

llvm-svn: 162700

llvm-svn: 162699

llvm-svn: 162698

to the -mllvm -mips-ssection-threshold=<value> pair and pass to the frontend.
The patch suggested by Carl Norum.

llvm-svn: 162697

coding standards.  Also, add stub for MSAsmStmt class as part of unifying 
codegen logic for AsmStmts.

llvm-svn: 162696

Also, add comments to addTrackNullOrUndefValueVisitor.

Thanks for the review, Anna!

llvm-svn: 162695

This test case is pretty bad, though.

llvm-svn: 162694

llvm-svn: 162693

llvm-svn: 162692

classes.

llvm-svn: 162691

parse doxygen comments for macros with libclang.

I'm not entirely happy about this script, but as it saves
a lot of work in keeping the docs up to date with the
actual code I think checking it in makes sense.

llvm-svn: 162690

Because the CXXNewExpr appears after the CXXConstructExpr in the CFG, we don't
actually have the correct region to construct into at the time we decide
whether or not to inline. The long-term fix (discussed in PR12014) might be to
introduce a new CFG node (CFGAllocator) that appears before the constructor.

Tracking the short-term fix in <rdar://problem/12180598>.

llvm-svn: 162689

llvm-svn: 162688

llvm-svn: 162687

intended functionality change. Thanks to Ahmed Charles for spotting it.

llvm-svn: 162686

llvm-svn: 162685

llvm-svn: 162684

llvm-svn: 162683

llvm-svn: 162682

This allows us to better reason about status objects, like Clang's own
llvm::Optional (when its contents are trivially destructible), which are
often intended to be passed around by value.

We still don't inline constructors for temporaries in the general case.

<rdar://problem/11986434>

llvm-svn: 162681

llvm-svn: 162680

llvm-svn: 162679