llvm-svn: 126037

without defining them.  This should be an error, but I'm paranoid about
"uses" that end up not actually requiring a definition.  I'll revisit later.

Also, teach IR generation to not set internal linkage on variable
declarations, just for safety's sake.  Doing so produces an invalid module
if the variable is not ultimately defined.

Also, fix several places in the test suite where we were using internal
functions without definitions.

llvm-svn: 126016

class and to bind the shared value using OpaqueValueExpr.  This fixes an
unnoticed problem with deserialization of these expressions where the
deserialized form would lose the vital pointer-equality trait;  or rather,
it fixes it because this patch also does the right thing for deserializing
OVEs.

Change OVEs to not be a "temporary object" in the sense that copy elision is
permitted.

This new representation is not totally unawkward to work with, but I think
that's really part and parcel with the semantics we're modelling here.  In
particular, it's much easier to fix things like the copy elision bug and to
make the CFG look right.

I've tried to update the analyzer to deal with this in at least some          
obvious cases, and I think we get a much better CFG out, but the printing
of OpaqueValueExprs probably needs some work.

llvm-svn: 125744

llvm-svn: 125694

llvm-svn: 125661

ends up in the text segment. // rdar://8825235.

llvm-svn: 125585

"used". Fixes <rdar://problem/8684363>.

llvm-svn: 125579

a zero constant for a complete class.  rdar://problem/8424975

To make this happen, track the field indexes for virtual bases
in the complete object.  I'm curious whether we might be better
off making CGRecordLayoutBuilder *much* more reliant on
ASTRecordLayout;  we're currently duplicating an awful lot of the ABI
layout logic.

llvm-svn: 125555

destruction in the destructor-aliases logic.  Fixes PR 9197.

llvm-svn: 125447

and we later find the definition, make sure that we add the definition
(not the declaration) to the list of deferred definitions to
emit. Fixes PR8864.

Thanks to Nick Lewycky for testing this	patch out

llvm-svn: 125157

mutable fields and with trivial destructors and copy constructors.

llvm-svn: 125073

llvm-svn: 125021

llvm-svn: 124988

Fix self-host; if a thunk already exists and has available_externally linkage, we should change its linkage instead of asserting.

llvm-svn: 124986

When building with optimizations, emit thunks with available_externally linkage so devirtualized function calls can also be de-thunked.

llvm-svn: 124984

won't assert when building a thunk for an implicit virtual member function that is not marked used.

llvm-svn: 124967

We now emit everything except unused implicit virtual member functions when building the vtable.

llvm-svn: 124935

abi.

llvm-svn: 124834

llvm-svn: 124781

This reopens PR99114, but that one at least can be avoided with an #include.
PR9130 cannot.

llvm-svn: 124780

is not defined in the current translation unit. Doing so lead to compile errors
such as PR9114.

Instead, when CodeGen is building the vtable, don't try to emit a definition
for functions that aren't marked used in the current translation unit.
Fixes PR9114.

llvm-svn: 124768

llvm-svn: 124757

llvm-svn: 124756

llvm-svn: 124753

llvm-svn: 124748

but has non-empty data fields, such as array of zero length,
remains zero.
// rdar://8945175

llvm-svn: 124741

bit-pattern.  It's not clear that this is actually useful given current
language restrictions.

llvm-svn: 124685

llvm-svn: 124654

extremely rambunctious, both on parsing and on template instantiation.
Calm it down, fixing an internal consistency assert on anonymous enum
instantiation manglings.

llvm-svn: 124653

llvm-svn: 124651

* llvm-link would complains about mismatched visibility
* If we produce a relocation with an available_externally, it is good to know that
it is hidden.

llvm-svn: 124633

Allow taking the address of such a field for a pointer-to-member constant. Fixes rdar://8818236.

llvm-svn: 124575

llvm-svn: 124574

current translation unit as available_externally. 

This helps devirtualize the second example in PR3100, comment 18:

struct S { S() {}; virtual void xyzzy(); };
inline void foo(S *s) { s->xyzzy(); }
void bar() { S s; foo(&s); }

This involved four major changes:

1. In DefineUsedVTables, always mark virtual member functions as referenced for
   non-template classes and class template specializations.
2. In CodeGenVTables::ShouldEmitVTableInThisTU return true if optimizations are
   enabled, even if the key function is not implemented in this translation 
   unit. We don't ever do this for code compiled with -fapple-kext, because we
   don't ever want to devirtualize virtual member function calls in that case.
3. Give the correct linkage for vtables where the key function is not defined.
4. Update the linkage for RTTI structures when necessary.

llvm-svn: 124565

llvm-svn: 124555

When emitting RTTI for a non-class type, compute the visibility of the RTTI data based on the explicit visibility of the type.

llvm-svn: 124553

I'm still not sure if having the typenames be visible with -hidden-weak-vtables, but I think it makes sense.

llvm-svn: 124549

llvm-svn: 124543

llvm-svn: 124540

Make emitting a VTT a two-step process, much like emitting a VTable. You first get the address of the VTT, and then pass it to EmitVTTDefinition.

llvm-svn: 124539