llvm-svn: 89613

When laying out bitfields, make sure that the data size is always aligned to a byte. This fixes PR5580.

llvm-svn: 89611

llvm-svn: 89610

with __INTPTR_TYPE__.

llvm-svn: 89609

llvm-svn: 89605

llvm-svn: 89604

llvm-svn: 89603

llvm-svn: 89598

llvm-svn: 89597

Undefined compound assignment result is checked in UndefinedAssignmentChecker. So this check is redundant.

llvm-svn: 89592

llvm-svn: 89591

llvm-svn: 89590

llvm-svn: 89587

llvm-svn: 89585

where long is only 32-bits and so a reinterpret_cast would be ill-formed.

llvm-svn: 89583

operand of an addressof operator, and so we should not treat it as an abstract
member-pointer expression and therefore suppress the implicit member access.

This is really a well-formedness constraint on expressions:  a DeclRefExpr of
a FieldDecl or a non-static CXXMethodDecl (or template thereof, or unresolved
collection thereof) should not be allowed in an arbitrary location in the AST.
Arguably it shouldn't be allowed anywhere and we should have a different expr
node type for this.  But unfortunately we don't have a good way of enforcing
this kind of constraint right now.

llvm-svn: 89578

llvm-svn: 89575

this information through lookup rather than rederiving it.

llvm-svn: 89570

llvm-svn: 89569

type and fixes a long-standing code gen. crash reported in
at least two PRs and a radar. (radar 7405040 and pr5025). 
There are couple of remaining issues that I would like for
Ted. and Doug to look at:

Ted, please look at failure in Analysis/MissingDealloc.m.
I have temporarily added an expected-warning to make the
test pass. This tests has a declaration of 'SEL' type which
may not co-exist with the new changes.

Doug, please look at a FIXME in PCHWriter.cpp/PCHReader.cpp.
I think the changes which I have ifdef'ed out are correct. They
need be considered for in a few Indexer/PCH test cases.

llvm-svn: 89561

Make FixedAddressChecker and experimental check; it currently produces a ton of false positives when analyzing some projects (e.g., Wine).

llvm-svn: 89560

llvm-svn: 89558

threading that state.

llvm-svn: 89557

 - Several important FIXMEs related to whether arguments are expressions or external names, and the mangling of extern "C" names (c.f., PR5522).

llvm-svn: 89556

 - Sometimes we have to mangle things we wouldn't normally (e.g., because they appear in a template expression).

 - This also tidies up the predicate to be more obvious what is getting mangled.

llvm-svn: 89555

Mangler: Strengthen invariants, MangleContext::mangleName should only be called on var or function decls.

llvm-svn: 89554

Mangler: Inline a bunch of functions into their sole caller, not that I don't love typing for typings sake, but...

llvm-svn: 89553

llvm-svn: 89552

llvm-svn: 89551

llvm-svn: 89550

llvm-svn: 89549

instead of requiring clients to make a raw_svector_ostream, which is just an
implementation detail.

llvm-svn: 89548

llvm-svn: 89547

llvm-svn: 89546

llvm-svn: 89545

into pretty much everything about overload resolution in order to wean
BuildDeclarationNameExpr off LookupResult::getAsSingleDecl().  Replace  
UnresolvedFunctionNameExpr with UnresolvedLookupExpr, which generalizes the
idea of a non-member lookup that we haven't totally resolved yet, whether by
overloading, argument-dependent lookup, or (eventually) the presence of   
a function template in the lookup results.  

Incidentally fixes a problem with argument-dependent lookup where we were 
still performing ADL even when the lookup results contained something from
a block scope.  

Incidentally improves a diagnostic when using an ObjC ivar from a class method.
This just fell out from rewriting BuildDeclarationNameExpr's interaction with
lookup, and I'm too apathetic to break it out.

The only remaining uses of OverloadedFunctionDecl that I know of are in
TemplateName and MemberExpr.

llvm-svn: 89544

The following attributes are currently supported in C++0x attribute
lists (and in GNU ones as well):
 - align() - semantics believed to be conformant to n3000, except for
   redeclarations and what entities it may apply to
 - final - semantics believed to be conformant to CWG issue 817's proposed
   wording, except for redeclarations
 - noreturn - semantics believed to be conformant to n3000, except for
   redeclarations
 - carries_dependency - currently ignored (this is an optimization hint)

llvm-svn: 89543

Add RegionStore test case that shows that floating point values are also implicitly tracked for undefined values.  (test case for <rdar://problem/6811085>).

llvm-svn: 89538

for -output-pch=.

llvm-svn: 89534

BasicStore.  In this example, BasicStore would lose information about
the pointer in path after '*path++', causing the analyzer to falsely
flag a null dereference.  This addresses <rdar://problem/7191542>.

llvm-svn: 89533