(Yes, I do intend to commit some tests for this.)

llvm-svn: 90818

llvm-svn: 90817

llvm-svn: 90800

llvm-svn: 90799

llvm-svn: 90796

llvm-svn: 90794

llvm-svn: 90780

llvm-svn: 90778

llvm-svn: 90751

(although it does pass regression tests).

llvm-svn: 90747

more accurate.

llvm-svn: 90746

llvm-svn: 90745

llvm-svn: 90723

generation, and make sure we generate thunks when the function is defined
rather than when the vtable is defined.

llvm-svn: 90722

llvm-svn: 90711

llvm-svn: 90709

llvm-svn: 90689

llvm-svn: 90687

Pass the desired vtable linkage to GenerateVtable directly. Only call MaybeMarkVirtualImplicitMembersReferenced for non-inline functions.

llvm-svn: 90686

llvm-svn: 90684

Only emit the vtable definition if the class has a key function and we're emitting it, or if the class doesn't have a key function and we are emitting the complete constructor.

llvm-svn: 90681

llvm-svn: 90680

llvm-svn: 90679

CodeGenModule::GenerateVtable now returns a pointer directly to the vtable and not to the address point.

llvm-svn: 90676

llvm-svn: 90675

llvm-svn: 90674

llvm-svn: 90673

Let the VTT builder pretend that getVtable returns a pointer to the vtable and not to the vtable address point.

llvm-svn: 90672

llvm-svn: 90671

llvm-svn: 90670

Factor vtable related GlobalVariable creation out into a separate function. Add vtable linkage test.

llvm-svn: 90667

to a memset or a memcpy from a global when possible.

llvm-svn: 90658

llvm-svn: 90657

llvm-svn: 90652

the side-effects of generating the methods in the vtable (including PR5676).

llvm-svn: 90635

llvm-svn: 90624

llvm-svn: 90622

llvm-svn: 90614

llvm-svn: 90610

llvm-svn: 90594