C99 mode.  This is a regression from an earlier patch of mine.

This also simplifies the linkage enums a bit.

llvm-svn: 69069

This will match gcc's behavior in the arena.

llvm-svn: 69061

llvm-svn: 69055

llvm-svn: 69054

llvm-svn: 69053

Add a tricky, tricky test case for PCH that we currently don't handle. Committed with a FIXME so that we don't forget it

llvm-svn: 69052

llvm-svn: 69051

llvm-svn: 69050

llvm-svn: 69049

Literal value calculation isn't likely to overflow on targets having int as 32 or less. Fixing the assert as it otherwise triggers for PIC16 which as i16 as int.

llvm-svn: 69046

pulling some attribute munging stuff into GetLinkageForFunction.

This should fix PR3986

llvm-svn: 69045

llvm-svn: 69044

wrap-up (e.g., turning tentative definitions into definitions). Also,
very that, when we actually use the PCH file, we get the ride code
generation for tentative definitions and definitions that show up in
the PCH file.

llvm-svn: 69043

This fixes <rdar://problem/6782722> XCDataTipsManager.m registers, observes notifications in class methods.

The radar above is the result of clang typing 'self' in a class method as 'Class', which results in some spurious warnings (GCC types 'self' in a class method as 'id').

I considered changing the type of 'self' to 'id' (to conform to GCC), however this resulted in *many* test cases breaking. In addition, I really prefer a more strongly typed 'self'.

All in all, this is the least obtrusive fix I could find for removing the spurious warnings (though we do loose some valid warnings).

llvm-svn: 69041

 - Pull out SetCommonAttributes, which handles the things common to
   aliases, methods, functions, and variables.

 - Pull out SetLLVMFunctionAttributesForDefinition, which handles the
   LLVM attributes which we only want to apply to a definition (like
   noinline and alwaysinline).

 - Kill SetGVDeclarationAttributes (inlined into SetFunctionAttributes
   and specialized).

 - Kill SetFunctionAttributesForDefinition (inlined into sole caller).

 - Inline SetGVDefinitionAttributes into SetMethodAttributes and
   specialize.

 - Rename SetGVDefinitionAttributes to SetFunctionDefinitionAttributes.

This is supposed to be a no functionality change commit, but I may
have made a mistake.

llvm-svn: 69036

 - No functionality change.

llvm-svn: 69035

disambiguate it.
 - No functionality change.

llvm-svn: 69034

llvm-svn: 69033

not in c89 mode).

llvm-svn: 69032

inlined for some reason, then we don't want a strong or even weak
definition.

llvm-svn: 69031

llvm-svn: 69030

llvm-svn: 69029

llvm-svn: 69028

llvm-svn: 69027

llvm-svn: 69026

llvm-svn: 69025

t.c:3:8: warning: extra tokens at end of #endif directive
#endif foo
       ^
       //

Don't do this in strict-C89 mode because bcpl comments aren't 
valid there, and it is too much trouble to analyze whether
C block comments are safe.

llvm-svn: 69024

Warning to properly report that it is an import/include_next instead of
claiming it is a #include.

llvm-svn: 69023

llvm-svn: 69022

llvm-svn: 69021

 - Exposed quite a few Sema issues and a CodeGen crash.

 - See FIXMEs in test case, and in SemaDecl.cpp (PR3983).

I'm skeptical that __private_extern__ should actually be a storage
class value. I think that __private_extern__ basically amounts to
  extern A __attribute__((visibility("hidden")))
and would be better off handled (a) as that, or (b) with an extra bit
in the VarDecl.

llvm-svn: 69020

 - No functionality change.

llvm-svn: 69019

delete it.

llvm-svn: 69018

deleting, not just the basic block.

llvm-svn: 69011

llvm-svn: 69010

llvm-svn: 69009

memory and aren't volatile.  This was interfering with
good scheduling.

llvm-svn: 69008

llvm-svn: 69007

Fix PR3934 part 2. findOnlyInterestingUse() was not setting IsCopy and IsDstPhys which are returned by value and used by callee. This happened to work on the earlier test cases because of a logic error in the caller side.

llvm-svn: 69006

non-inline external definitions (and tentative definitions) that are
found at the top level. The corresponding declarations are stored in a
record in the PCH file, so that they can be provided to the
ASTConsumer (via HandleTopLevelDecl) when the PCH file is read.

llvm-svn: 69005