llvm-svn: 61894

llvm-svn: 61888

llvm-svn: 61886

Fix printing of member references to avoid displaying implicitly-generated member references, e.g., for anonymous struct/unions or implicit 'this' in member functions

llvm-svn: 61885

of category implementation is undeclared. Issue error instead.

llvm-svn: 61882

method on 'super' receiver in a category implementation.
Other simpler cases were working by accident.

llvm-svn: 61880

Duplicate-member checking within classes is still a little messy, and
anonymous unions are still completely broken in C. We'll need to unify
the handling of fields in C and C++ to make this code applicable in
both languages.

llvm-svn: 61878

"fake" options, allowing Tools to be oblivious to whether an argument
is real or synthetic. This kills off DerivedArg & a number of FIXMEs.

llvm-svn: 61871

instances; this just complicated things and doesn't seem to provide
any benefit.

llvm-svn: 61869

Add ObjCContainerDecl class and have ObjCInterfaceDecl/ObjCCategoryDecl/ObjCProtocolDecl inherit from it.

llvm-svn: 61866

Use DeclContext::getLookupContext wherever necessary to ensure that we look through transparent contexts

llvm-svn: 61861

llvm-svn: 61860

out its lookup context (to see through linkage
specifications). Addresses <rdar://problem/6477142>.

llvm-svn: 61848

(for killing off DerivedArg).

llvm-svn: 61846

the ArgList.

llvm-svn: 61844

llvm-svn: 61843

structures and classes) in C++. Covers name lookup and the synthesis
and member access for the unnamed objects/fields associated with
anonymous unions.

Some C++ semantic checks are still missing (anonymous unions can't
have function members, static data members, etc.), and there is no
support for anonymous structs or unions in C.

llvm-svn: 61840

recent discussions with Thomas Clement and Ken Ferry concerning the "fundamental
rule" for Cocoa memory management
(http://developer.apple.com/documentation/Cocoa/Conceptual/MemoryMgmt/Tasks/MemoryManagementRules.html).

Here is the revised behavior of the checker concerning tracking retain/release
counts for objects returned from message expressions involving instance methods:

1) Track the returned object if the return type of the message expression is
id<..>, id, or a pointer to *any* object that subclasses NSObject. Such objects
are assumed to have a retain count. Previously the checker only tracked objects
when the receiver of the message expression was part of the standard Cocoa API
(i.e., had class names prefixed with 'NS'). This should significantly expand the
amount of checking performed.

2) Consider the object owned if the selector of the message expression contains
"alloc", "new", or "copy". Previously we also considered "create", but this
doesn't follow from the fundamental rule (discussions with the Cocoa folks
confirms this).

llvm-svn: 61837

llvm-svn: 61833

nested in the translation unit. This fixes <rdar://problem/6476070>.

llvm-svn: 61832

- Big Idea:
   Source files are now mmaped when ContentCache::getBuffer() is first called.
   While this doesn't change the functionality when lexing regular source files,
   it can result in source files not being paged in when using PTH.

- Performance change:
  - No observable difference (-fsyntax-only/-Eonly) on Cocoa.h when doing
    regular source lexing.
  - No observable time difference (-fsyntax-only/-Eonly) on Cocoa.h when using
    PTH. We do observe, however, a reduction of 279K in memory mapped source
    code (3% reduction). The majority of pages from Cocoa.h (and friends) are
    still being pulled in, however, because any literal will cause
    Preprocessor::getSpelling() to be called (causing the source for the file to
    get pulled in). The next possible optimization is to cache literal strings
    in the PTH file to avoid the need for the original header sources entirely.

- Right now there is a preprocessor directive to toggle between "lazy" and
  "eager" creation of MemBuffers. This is not permanent, and is there in the
  short term to just test additional optimizations.

llvm-svn: 61827

Remove redunant (and incorrect) call to SourceManager::PrintStats().  This would be called after a SourceManager was 'cleared', so it printed bogus results.  Moreover, these stats are already printed earlier in the code path.

llvm-svn: 61825

llvm-svn: 61821

Add whitespace to silence the following warning in a Release build: warning: suggest a space before ';' or explicit braces around empty body in 'while' statement

llvm-svn: 61820

Return UnknownVal in RegionStoreManager::getSizeInElements() for unsupported regions.  This silences a warning when compiling Release-Asserts builds.

llvm-svn: 61818

to track down, easy to fix. This is on going.

llvm-svn: 61817

Fix <rdar://problem/5956221> clang ObjC rewriter: Microsoft-specific __fastcall keyword unrecognized.

This fix is C++ specific.

llvm-svn: 61816

llvm-svn: 61815

- Simplify ParseDeclCXX to use early exit on error instead of nesting.
- Change ParseDeclCXX to using the 'skip on error' form of ExpectAndConsume.
- If we don't see the ; in a using directive, still call the action, for 
  hopefully better error recovery.

llvm-svn: 61801

llvm-svn: 61800

llvm-svn: 61799

llvm-svn: 61798

llvm-svn: 61797

MaybeParseTypeSpecifier -> ParseOptionalTypeSpecifier.

llvm-svn: 61796

llvm-svn: 61795

llvm-svn: 61794

driver to lookup this way instead of manually scanning arguments in
multiple places.

llvm-svn: 61793

llvm-svn: 61792

llvm-svn: 61791

llvm-svn: 61790