llvm-svn: 49805

llvm-svn: 49804

to the plug-in GRTransferFuncs object.

llvm-svn: 49801

are referenced by CFGBlock terminators.

llvm-svn: 49798

two worklists: for nodes whose locations are block edges with loop terminators
and another for nodes with all other locations.  We only dequeue from the loop
worklist when the other is empty.  Exploration of the graph is still in
reverse-BFS.

llvm-svn: 49791

llvm-svn: 49781

llvm-svn: 49780

allowing us to use a cheaper means to highlight keywords and making
it so that comments won't foul up macro expansions.

Start highlighting macro expansions.

llvm-svn: 49779

problems, including the fact that it doesn't work well with multi-line 
comments due to Ted's crazy table.  However, that could be fixed, and it
does work with single-line ones :).

llvm-svn: 49778

rewriter, getting sourcelocations out of the picture.

llvm-svn: 49775

a SourceLocation to get a RewriteBuffer, poke the RewriteBuffer
with an offset directly.  THis is no faster, but results in 
cleaner code.

llvm-svn: 49774

immutable smart pointer (we don't need to pass references, just pass Selector).

llvm-svn: 49773

llvm-svn: 49771

speeds up -emit-html on ted's testcase by 29% (.138 -> 0.107s) in a
release build.

llvm-svn: 49767

llvm-svn: 49763

llvm-svn: 49756

to start logically organizing them.

Added initial plug-in transfer function support for Objective-C message expressions.

llvm-svn: 49752

as before r49748 (where BlockVarDecl was removed).

llvm-svn: 49749

Remove FileVarDecl and BlockVarDecl. They are replaced by VarDecl::isBlockVarDecl() and VarDecl::isFileVarDecl().

This is a fairly mechanical/large change. As a result, I avoided making any changes/simplifications that weren't directly related. I did break two Analysis tests. I also have a couple FIXME's in UninitializedValues.cpp. Ted, can you take a look? If the bug isn't obvious, I am happy to dig in and fix it (since I broke it).

llvm-svn: 49748

llvm-svn: 49742

Fix bug in terminator processing for uninitialized-values: simply ignore the terminator, don't reprocess it.

LiveVariables analysis now does a flow-insensitive analysis to determine what variables have their address taken; these variables are now always treated as being live.

The DataflowSolver now uses "SetTopValue()" when getting the initial value for the entry/exit block.

llvm-svn: 49734

llvm-svn: 49727

llvm-svn: 49712

llvm-svn: 49711

in a block's terminator.  This expression is visited within a block, but it is accessed by the
terminator.  This is important to observe because for live-variables analysis the block-level
expression is live between the terminator and where the expression occurs in the block.  So far
this hasn't been an issue to not observe this because the block-level expression used in the
terminator is always the last one in the block, and we have never queried the liveness information
about this point (but before the terminator).

llvm-svn: 49709

in a DeclStmt.

llvm-svn: 49708

"Alive" as opposed to staying the same.

llvm-svn: 49707

is still live.

llvm-svn: 49705

llvm-svn: 49703

llvm-svn: 49699

the new RHS directly instead of indirecting through the 'InsertResult'
struct.  This eliminates InsertResult.

llvm-svn: 49694

llvm-svn: 49689

of errors.

llvm-svn: 49686

the files of different SourceLocations.  These methods correctly handle the
case where a file may have multiple FileIDs due to it being large enough
to be spread across several chunks.

llvm-svn: 49682

llvm-svn: 49679

llvm-svn: 49678

is the one attached to the Diagnostic object.

llvm-svn: 49677

llvm-svn: 49672

llvm-svn: 49668

llvm-svn: 49664