llvm-svn: 91155

llvm-svn: 91154

llvm-svn: 91153

llvm-svn: 91152

llvm-svn: 91149

in a file context.  In well-formed code, only happens with friend functions.
Fixes PR 5760.

llvm-svn: 91146

llvm-svn: 91141

informative chunk.

llvm-svn: 91139

llvm-svn: 91138

llvm-svn: 91137

correctly.

llvm-svn: 91136

specializations and class template partial specializations (they're
never named directly). Also, member access expressions only refer to
value declarations (fields, functions, enumerators, etc.) and
Objective-C property declarations; filter out everything else.

llvm-svn: 91133

XFAIL this for now, fixing linkage bugs causes the order of globals to change. Will fix later today.

llvm-svn: 91130

llvm-svn: 91129

llvm-svn: 91127

llvm-svn: 91125

llvm-svn: 91119

llvm-svn: 91118

for logical not.

llvm-svn: 91112

llvm-svn: 91108

Enhance understanding of VarRegions referenced by a block whose declarations are outside the current stack frame.  Fixes <rdar://problem/7462324>.

llvm-svn: 91107

llvm-svn: 91100

llvm-svn: 91099

Improve linkage of RTTI data structures. Introduce CodeGenModule::GetAddrOfRTTI which figures out the right linkage of the RTTI information for the given type and whether it should be defined or not. I will migrate clients over to GetAddrOfRTTI in subsequent commits (with tests).

llvm-svn: 91098

llvm-svn: 91097

doing any of the other redeclaration checks.  We were missing a few cases.
Fixes PR 5752.

llvm-svn: 91096

is difficult because they're so terribly, terribly ambiguous.


We implement access declarations in terms of using declarations, which is
quite reasonable.  However, we should really persist the access/using
distinction in the AST and use the appropriate name in diagnostics.  This
isn't a priority, so I'll just file a PR and hope someone else does it. :)

llvm-svn: 91095

Give the "cannot pass object of non-POD type 'class C' through variadic constructor; call will abort at runtime" warning a -W flag (non-pod-varargs) and default it being an error by default.  There is no good reason to allow users to get bitten by this sort of thing by default.

llvm-svn: 91094

llvm-svn: 91089

llvm-svn: 91088

When extending the lifetime of a temporary, make sure to emit a branch to the cleanup exit block. This fixes a broken module error in LLVMCConfigurationEmitter.cpp.

llvm-svn: 91086

llvm-svn: 91085

When an exception needs to be freed by calling __cxa_exception_free, make sure to stash away the exception pointer somewhere. 

This fixes an "Instruction does not dominate all uses!" verification error when compiling TableGen.

llvm-svn: 91084

llvm-svn: 91083

inconsistent situations if we do, and they are not important for PCH performance
(which currently only needs the stats to construct the initial FileManager
entries).
 - No test case, sorry, the machinations are too involved.

This occurs when, for example, the build makes a PCH file and has a header map
or a -I for a directory that does not yet exist. It is possible we will cache
the negative stat on that directory, and then in the build we will never find
header files inside that dir.

For PCH we don't need these stats anyway for performance, so this also makes PCH
files smaller w/ no loss. I hope to eventually eliminate the stat cache
entirely.

llvm-svn: 91082

objective-c++ mode and also removed dead-code in this area.
(fixes radar 7456710).

llvm-svn: 91081

llvm-svn: 91080

llvm-svn: 91079

llvm-svn: 91078

block, if the function is supposed to return a value as we don't know
exactly what the asm code does.

llvm-svn: 91073