llvm-svn: 149996

llvm-svn: 149995

llvm-svn: 149994

llvm-svn: 149990

in objective-c rewriter. wip.

llvm-svn: 149989

Parsing of @implementations was based on modifying global state from
the parser; the logic for late parsing of methods was spread in multiple places
making it difficult to have a robust error recovery.

  -it was difficult to ensure that we don't neglect parsing the lexed methods.
  -it was difficult to setup the original objc container context for parsing the lexed methods
   after completing ParseObjCAtImplementationDeclaration and returning to top level context.

Enhance parsing of @implementations by centralizing it in Parser::ParseObjCAtImplementationDeclaration().
ParseObjCAtImplementationDeclaration now returns only after an @implementation is fully parsed;
all the data and logic for late parsing of methods is now in one place.

This allows us to provide code-completion for late parsed methods with mis-matched braces.
rdar://10775381

llvm-svn: 149987

Clang miscompiles it under certain circumstances, and it's a good exercise for APInt.

llvm-svn: 149986

Patch by Eitan Adler

llvm-svn: 149984

llvm-svn: 149982

llvm-svn: 149981

llvm-svn: 149980

  - Capturing variables by-reference and by-copy within a lambda
  - The representation of lambda captures
  - The creation of the non-static data members in the lambda class
  that store the captured variables
  - The initialization of the non-static data members from the
  captured variables
  - Pretty-printing lambda expressions

There are a number of FIXMEs, both explicit and implied, including:
  - Creating a field for a capture of 'this'
  - Improved diagnostics for initialization failures when capturing
  variables by copy
  - Dealing with temporaries created during said initialization
  - Template instantiation
  - AST (de-)serialization
  - Binding and returning the lambda expression; turning it into a
  proper temporary
  - Lots and lots of semantic constraints
  - Parameter pack captures

llvm-svn: 149977

llvm-svn: 149976

llvm-svn: 149975

llvm-svn: 149974

llvm-svn: 149973

llvm-svn: 149972

llvm-svn: 149971

load / store) if the ADD / SUB has a live definition of CPSR.

Bug reported by David Meyer. Alas, no test case.

llvm-svn: 149970

llvm-svn: 149968

llvm-svn: 149967

llvm-svn: 149966

llvm-svn: 149965

llvm-svn: 149964

Make FunctionDecl::doesDeclarationForceExternallyVisibleDefinition use the same logic as FunctionDecl::isInlineDefinitionExternallyVisible to figure out whether to emit a definition.  Based on work by Anton Yartsev.

llvm-svn: 149963

llvm-svn: 149962

llvm-svn: 149961

Create PathDiagnosticCallEnter and PathDiagnosticCallExit, to remark calls in PathDiagnostics from other events.  This will
have potential uses later.

llvm-svn: 149960

llvm-svn: 149959

llvm-svn: 149958

llvm-svn: 149954

MaxEditDistance was effectively unused as it being initialized to the max
unsigned valued but never updated. Removing it avoids conversion
headaches once the "edit distance" of a typo correction is a weighted
composite of several values instead of roughly the number of characters
changed; comparing the weighted composite value to the number of
characters in a typo would require some form of normalization to make it
comparable to the old, character-based notion of edit distance.

llvm-svn: 149953

much. This gets us an addition 0.9% on 445.gobmk.

llvm-svn: 149952

These are new options that gcc doesn't recognize so the clang driver needs
to remove them when it falls back to invoking gcc.

llvm-svn: 149951

llvm-svn: 149949

separately.

llvm-svn: 149947

llvm-svn: 149945

llvm-svn: 149944

llvm-svn: 149943

llvm-svn: 149942