llvm-svn: 76955

TryEvaluateBool instead of using a raw 'int'.  This avoids any
confusion of how 'int' converts to bool, and makes the resultant code
easier to read.

Condense a bunch of 'addSuccessor()' calls in 'if ... else' to use the
ternary operator instead.

llvm-svn: 76947

llvm-svn: 76911

llvm-svn: 76814

llvm-svn: 76795

llvm-svn: 76531

llvm-svn: 76530

llvm-svn: 76529

llvm-svn: 76522

llvm-svn: 76500

Fix some fallout from CFGBuilder restructuring: all expressions that we explicitly handle have the possibility to be block-level expressions.

llvm-svn: 76277

llvm-svn: 76261

is an algorithm that is much easier to understand and slightly more efficient.
Thanks to Mike Stump for our discussions on the CFGBuilder and his comments that
helped prompt this long needed cleanup.

llvm-svn: 76250

llvm-svn: 76205

llvm-svn: 76202

llvm-svn: 76196

llvm-svn: 76180

code with the new method.

llvm-svn: 76164

conventions.  Also reflowed comments and removed spaces at end of
lines and fixed up 80 col violations.

llvm-svn: 76140

llvm-svn: 76133

llvm-svn: 76092

block would get hooked up in some cases when processing empty compound
statements.

llvm-svn: 74743

This is simple enough, but then I thought it would be nice to make PrintingPolicy
get a LangOptions so that various things can key off "bool" and "C++" independently.
This spiraled out of control.  There are many fixme's, but I think things are slightly
better than they were before.

One thing that can be improved: CFG should probably have an ASTContext pointer in it,
which would simplify its clients.

llvm-svn: 74493

llvm-svn: 74131

llvm-svn: 74085

printing logic to help customize the output. For now, we use this
rather than a special flag to suppress the "struct" when printing
"struct X" and to print the Boolean type as "bool" in C++ but "_Bool"
in C.

llvm-svn: 72590

block. This makes it a little easier for diagnostics generation.

llvm-svn: 71037

llvm-svn: 70620

expressions not yet properly handled by the CFGBuilder. This failure resulted in
a null CFGBlock* being used in rare cases (causing a crash).

llvm-svn: 70612

llvm-svn: 70284

llvm-svn: 70280

- Add 'LoopTarget' pointer field to CFGBlock. This records if the block is used
  as the 'loop back' path back to the head of a loop.
- For ForStmt, encode the loop back target as the increment code.

llvm-svn: 70274

llvm-svn: 68533

had too many false positives in the analyzer.

llvm-svn: 68492

distinguish between the true and false branches for path-sensitive analyses.

llvm-svn: 68185

assume that @catch blocks are never executed.

llvm-svn: 68072

llvm-svn: 67928

llvm-svn: 67923

llvm-svn: 65519

by DeclContexts (always) rather than by statements. 

DeclContext currently goes out of its way to avoid destroying any
Decls that might be owned by a DeclGroupOwningRef. However, in an
error-recovery situation, a failure in a declaration statement can
cause all of the decls in a DeclGroupOwningRef to be destroyed after
they've already be added into the DeclContext. Hence, DeclContext is
left with already-destroyed declarations, and bad things happen. This
problem was causing failures that showed up as assertions on x86 Linux
in test/Parser/objc-forcollection-neg-2.m.

llvm-svn: 64474