llvm-svn: 41870

llvm-svn: 41869

This method is used to determine if an expression contains implicit
control-flow, and thus appears in a distinct statement slot in the CFG.

For example:

  (1) x = ... ? ... ? ...

  logically becomes:

  (1) ... ? ... : ...  (a unique statement slot for the ternary ?)
  (2) x = [E1]         (where E1 is actually the ConditionalOperator*)

A client of the CFG, when walking the statement at (2), will encounter
E1.  In this case, hasImplicitControlFlow(E1) == true, and the client
will know that the expression E1 is explicitly placed into its own statement
slot to capture the implicit control-flow it has.

llvm-svn: 41868

where not reversing the order of their subexpression blocks.

Added feature where CallExprs are placed in their own statement slot in
a CFGBlock.  Thus we have a designated "return site" within a CFGBlock when
reasoning about function calls.

llvm-svn: 41866

- Add an ObjcIvarDecl AST node (a subclass of FieldDecl).
- Instantiate the node in Sema::ParseField(), based on the type of the TagDecl.
- Add Sema::ObjcAddInstanceVariable(), responsible for adorning/adding the ObjcIvarDecl.

llvm-svn: 41864

llvm-svn: 41863

llvm-svn: 41862

llvm-svn: 41861

llvm-svn: 41860

llvm-svn: 41859

access to bits).  Use them in place of float and
double interfaces where appropriate.
First bits of x86 long double constants handling 
(untested, probably does not work).

llvm-svn: 41858

llvm-svn: 41855

llvm-svn: 41854

if the assigned value is a constant expression, e.g.:

int x = 0;

We then check to see if "x" is ever reassigned later.  If so, we don't
emit a warning.  This is because programmers frequently use defensive
programming to make sure a variable has a defined value.

llvm-svn: 41853

information for EH.

llvm-svn: 41852

llvm-svn: 41851

llvm-svn: 41850

llvm-svn: 41849

llvm-svn: 41848

warnings that some compilers diagnose

llvm-svn: 41847

the underlying nested function.

llvm-svn: 41846

of their elements do not yield the same ParamAttrsList,
though they should.  On the other hand, everyone seems
to pass such vectors with elements ordered by increasing
index, so rather than sorting the elements simply assert
that the elements are ordered in this way.

llvm-svn: 41845

nested function.

llvm-svn: 41844

init_trampoline.  There is now only one
trampoline intrinsic.

llvm-svn: 41841

llvm-svn: 41840

that global stub instead of doing the ".set" thingy we were doing before.

llvm-svn: 41838

based on whether the key AND the value require ctors/dtors.

llvm-svn: 41837

keys.

llvm-svn: 41834

llvm-svn: 41833

Fix bugs with &=, intersect with complement. Add three argument version of intersect with complement.

llvm-svn: 41832

llvm-svn: 41831

llvm-svn: 41830

llvm-svn: 41829

llvm-svn: 41826

llvm-svn: 41824

llvm-svn: 41823

llvm-svn: 41822

llvm-svn: 41821

llvm-svn: 41820

llvm-svn: 41819