ASTUnit::LoadFromCompilerInvocation() fails to create target
information.

llvm-svn: 98697

returning objc objects. There will be a corresponding objective-c++
patch soon.

llvm-svn: 98696

llvm-svn: 98695

literal. Fixes radar 7760213.

llvm-svn: 98693

llvm-svn: 98691

buffer was invalid when it was created, and use that bit to always set
the "Invalid" flag according to whether the buffer is invalid. This
ensures that all accesses to an invalid buffer are marked invalid,
improving recovery.

llvm-svn: 98690

recovery for those that need it.

llvm-svn: 98689

llvm-svn: 98688

llvm-svn: 98685

llvm-svn: 98684

llvm-svn: 98682

that occur in constructors (on the unwind path).

llvm-svn: 98681

at least give the Apple ABI a name that reflects Apple in prep for other ABI specs that might come along

llvm-svn: 98678

llvm-svn: 98676

Invalid bit through; there are no safety-critical callers of these
functions.

llvm-svn: 98674

them to recover more gracefully on failure.

llvm-svn: 98672

needs better error recovery.

llvm-svn: 98667

SourceManager versions), updating those callers that need to recover
gracefully from failure.

llvm-svn: 98665

llvm-svn: 98664

building mainline GCC, PR6542

llvm-svn: 98661

llvm-svn: 98655

llvm-svn: 98639

presence or absence of header map arguments when using the precompiled
header would cause Clang to get confused about which headers had
already been included/imported, along with their controlling
macros. The fundamental problem is that the serialization of the
header search information was relying on the UIDs of FileEntry objects
at PCH generation time and PCH load time to be equivalent, which
effectively means that we had to probe the same files in the same
order. Differing header map arguments caused an extra FileEntry
lookup, but it's easy to imagine other minor command-line arguments
triggering this problem.

Header-search information is now encoded along with the
source-location entry for a file, so that we register information
about a file's properties as a header at the same time we create the
FileEntry for that file.

Fixes <rdar://problem/7743243>.

llvm-svn: 98636

llvm-svn: 98631

llvm-svn: 98630

since RemoveDeadBinding mistakenly remove the binding to CXXThisRegion. 

llvm-svn: 98629

constructors from implicitly-defined members.

llvm-svn: 98614

<rdar://problem/7735566>.

llvm-svn: 98613

destructor definitions.  Remove some code duplication.

llvm-svn: 98611

required when emitting a destructor definition.

llvm-svn: 98609

SourceManager's getBuffer() and, therefore, could fail, along with
Preprocessor::getSpelling(). Use the Invalid parameters in the literal
parsers (string, floating point, integral, character) to make them
robust against errors that stem from, e.g., PCH files that are not
consistent with the underlying file system.

I still need to audit every use caller to all of these routines, to
determine which ones need specific handling of error conditions.

llvm-svn: 98608

simplifying the SourceManager interfaces somewhat.

llvm-svn: 98598

and start simplifying the interfaces in SourceManager that can fail.

llvm-svn: 98594

llvm-svn: 98591

llvm-svn: 98587

SourceManager's getBuffer() (and similar) operations. This abstract
can be used to force callers to cope with errors in getBuffer(), such
as missing files and changed files. Fix a bunch of callers to use the
new interface.

Add some very basic checks for file consistency (file size,
modification time) into ContentCache::getBuffer(), although these
checks don't help much until we've updated the main callers (e.g.,
SourceManager::getSpelling()).

llvm-svn: 98585

Also change this method to lookup property declarations using DeclContext::lookup().

llvm-svn: 98574

property decls using DeclContext::lookup().

llvm-svn: 98571

llvm-svn: 98570

llvm-svn: 98560