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

 a) legal
 b) likely to be chosen as the official mangling

This will break ABI compatibility with all literal operator names,
so you may need to recompile any such code. Sorry.

llvm-svn: 90587

llvm-svn: 90586

When generating a virtual destructor, don't try to make a virtual call to the base class destructor because then we'll just re-enter the same destructor!

This was done to fix PR5619, so I went ahead and passed a dummy VTT pointer for now.

llvm-svn: 90578

llvm-svn: 90576

the end of all the catches.

llvm-svn: 90574

llvm-svn: 90573

llvm-svn: 90571

llvm-svn: 90570

llvm-svn: 90569

llvm-svn: 90568

llvm-svn: 90565

llvm-svn: 90563

llvm-svn: 90562

llvm-svn: 90561

llvm-svn: 90544