llvm-svn: 121378

"inline", we weren't giving the definition weak linkage because the
"inline" bit wasn't propagated. This was a longstanding FIXME that,
somehow, hadn't triggered a bug in the wild. Fix this problem by
tracking whether any declaration was marked "inline", and clean up the
semantics of GNU's "extern inline" semantics calculation based on this
change.

Fixes <rdar://problem/8740363>.

llvm-svn: 121373

llvm-svn: 121363

llvm-svn: 121352

Before determining the effect the alignment of base struct will have in the aligment of the sub-struct,
take into account if the sub-struct is packed and its maximum field alignment.

Fixes rdar://8745206

llvm-svn: 121335

llvm-svn: 121333

llvm-svn: 121326

declaration that is a value in ill-formed code. Instead of crashing,
treat this as a dependent typename specifier and suggest that the
using add "typename" into the using declaration. Fixes <rdar://problem/8740998>.

llvm-svn: 121322

llvm-svn: 121302

Remove the "splat" parameter from the EmitNeonCall function, since it is no
longer needed.

llvm-svn: 121300

llvm-svn: 121298

llvm-svn: 121288

llvm-svn: 121284

llvm-svn: 121277

implementation.

llvm-svn: 121263

Fixes rdar://8739801.

llvm-svn: 121228

llvm-svn: 121221

llvm-svn: 121214

llvm-svn: 121210

the failed compile in PR8751.

llvm-svn: 121192

llvm-svn: 121191

llvm-svn: 121189

llvm-svn: 121188

(@synthesize and @dynamic).

llvm-svn: 121159

llvm-svn: 121143

llvm-svn: 121139

llvm-svn: 121137

zextOrTrunc(), and APSInt methods extend(), extOrTrunc() and new method
trunc(), to be const and to return a new value instead of modifying the
object in place.

llvm-svn: 121121

llvm-svn: 121097

llvm-svn: 121084

I'm not opposed to the idea in concept, but there's no point in preserving
abortive experiments.

llvm-svn: 121083

llvm-svn: 121081

New AST node introduced: BinaryTypeTraitExpr; to be reused for more intrinsics.

llvm-svn: 121074

llvm-svn: 121073

cv-qualification conversions. More specifically, there's an implicit
cv-qualification conversion (even one that drops qualifiers) when
converting to 'id' or qualified 'id'. Fixes <rdar://problem/8734046>.

llvm-svn: 121047

FunctionArrayLvalueConversion but without the function/array decay.  Generally
this is only appropriate for use sites that know the type of the expression
and thus that it can't be subject to the decays.

Also make sure we do lvalue-to-rvalue on the bases of ivar references.

llvm-svn: 121035

llvm-svn: 121029

introduced in r121023.

llvm-svn: 121025

My previous attempt at solving the compile-time problem with many
redeclarations of the same entity cached both linkage and visibility,
while this patch only tackles linkage. There are several reasons for
this difference:

  - Linkage is a language concept, and is evaluated many times during
    semantic analysis and codegen, while visibility is only a
    code-generation concept that is evaluated only once per (unique)
    declaration. Hence, we *must* optimize linkage calculations but
    don't need to optimize visibility computation.
  - Once we know the linkage of a declaration, subsequent
    redeclarations can't change that linkage. Hence, cache
    invalidation is far simpler than for visibility, where a later
    redeclaration can completely change the visibility.
  - We have 3 spare bits in Decl to store the linkage cache, so the
    cache doesn't increase the size of declarations. With the
    visibility+linkage cache, NamedDecl got larger.

llvm-svn: 121023

Fixes PR8742.

llvm-svn: 121022