| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| |
|
|
|
|
|
| |
optimization. Make sure to require a vtable when trying to get the address
of a VTT, otherwise we would never end up emitting the VTT.
llvm-svn: 131400
|
| |
|
|
|
|
| |
a bit messy, but it is correct as long as the method in question doesn't use indirect gotos. A couple of possible alternative implementations are outlined in FIXME's in this patch. rdar://problem/8077308 .
llvm-svn: 130993
|
| |
|
|
|
|
| |
change.
llvm-svn: 130699
|
| |
|
|
|
|
| |
one half of PR9660.
llvm-svn: 129252
|
| |
|
|
|
|
| |
functions in the class.
llvm-svn: 129250
|
| |
|
|
|
|
|
| |
Change the return type of CodeGenVTables::getVirtualBaseOffsetOffset() to
CharUnits. No change in functionality intended.
llvm-svn: 129072
|
| |
|
|
|
|
|
|
|
| |
with debug info.]
Use CharUnits for the offsets in the VirtualBaseClassOffsetOffsetsMapTy. No
change in functionality intended.
llvm-svn: 129048
|
| |
|
|
|
|
|
|
|
| |
info.]
Use CharUnits for the offset type in the ClassNamesAndOffsets map in
dumpLayout(). No change in functionality intended.
llvm-svn: 129046
|
| |
|
|
|
|
|
| |
Use CharUnits for the offsets in the VBaseOffsetOffsetsMapTy types. No
change in functionality intended.
llvm-svn: 129043
|
| |
|
|
| |
llvm-svn: 128842
|
| |
|
|
|
|
| |
CharUnits. No change in functionality intended.
llvm-svn: 128776
|
| |
|
|
|
|
| |
change in functionality intended.
llvm-svn: 128773
|
| |
|
|
|
|
| |
dumpLayout(). No change in functionality intended.
llvm-svn: 128771
|
| |
|
|
|
|
| |
change in functionality intended.
llvm-svn: 128770
|
| |
|
|
|
|
| |
functionality intended.
llvm-svn: 128756
|
| |
|
|
|
|
| |
CharUnits. No change in functionality intended.
llvm-svn: 128754
|
| |
|
|
|
|
| |
functionality intended.
llvm-svn: 128753
|
| |
|
|
|
|
| |
No change in functionality intended.
llvm-svn: 128752
|
| |
|
|
|
|
|
| |
VCallAndVBaseOffsetBuilder::getCurrentOffsetOffset() to CharUnits. No change
in functionality intended.
llvm-svn: 128603
|
| |
|
|
|
|
|
| |
VCallAndVBaseOffsetBuilder::AddVBaseOffsets() to CharUnits. No change in
functionality intended.
llvm-svn: 128600
|
| |
|
|
|
|
| |
constructor to CharUnits. No change in functionality intended.
llvm-svn: 128598
|
| |
|
|
|
|
|
| |
VCallAndVBaseOffsetBuilder::AddVCallAndVBaseOffsets() to
CharUnits. No change in functionality intended.
llvm-svn: 128596
|
| |
|
|
|
|
| |
PHINode::Create() giving the (known or expected) number of operands.
llvm-svn: 128538
|
| |
|
|
|
|
|
| |
VCallAndVBaseOffsetBuilder::AddVCallOffsets() to CharUnits. No change in
functionality intended.
llvm-svn: 128531
|
| |
|
|
|
|
| |
functionality intended.
llvm-svn: 128522
|
| |
|
|
|
|
| |
intended.
llvm-svn: 128521
|
| |
|
|
|
|
| |
to CharUnits. No change in functionality intended.
llvm-svn: 128520
|
| |
|
|
|
|
| |
CharUnits. No change in functionality intended.
llvm-svn: 128516
|
| |
|
|
|
|
| |
No change in functionality intended.
llvm-svn: 128393
|
| |
|
|
|
|
| |
functionality intended.
llvm-svn: 128392
|
| |
|
|
|
|
| |
functionality intended.
llvm-svn: 128391
|
| |
|
|
|
|
| |
CharUnits).
llvm-svn: 128386
|
| |
|
|
|
|
| |
functionality intended.
llvm-svn: 128385
|
| |
|
|
|
|
| |
CharUnits. No change in functionality intended.
llvm-svn: 128384
|
| |
|
|
|
|
| |
functionality intended.
llvm-svn: 128383
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Emit them instead with the linkage of the VTT.
I'm actually really ambivalent about this; it's what GCC does, but outside
of improving code size (if the linkage is coalescing), I'm not sure it's
at all relevant. Construction vtables are naturally referenced only by the
VTT, which is itself only referenced by complete-object constructors and
destructors; giving the construction vtables possibly-external linkage is
important if you have an optimization that drills through the VTT to a
reference to a particular construction vtable which it cannot just emit
itself.
llvm-svn: 128374
|
| |
|
|
|
|
|
|
|
| |
platform implies default visibility. To achieve these, refactor our
lookup of explicit visibility so that we search for both an explicit
VisibilityAttr and an appropriate AvailabilityAttr, favoring the
VisibilityAttr if it is present.
llvm-svn: 128336
|
| |
|
|
|
|
|
| |
FinalOverriders::ComputeBaseOffsets() to CharUnits. No change in
functionality intended.
llvm-svn: 128323
|
| |
|
|
|
|
| |
intended.
llvm-svn: 128321
|
| |
|
|
|
|
| |
functionality intended.
llvm-svn: 128318
|
| |
|
|
|
|
| |
functionality intended.
llvm-svn: 128317
|
| |
|
|
|
|
| |
intended.
llvm-svn: 128315
|
| |
|
|
|
|
| |
change in functionality intended.
llvm-svn: 128190
|
| |
|
|
| |
llvm-svn: 127494
|
| |
|
|
| |
llvm-svn: 127319
|
| |
|
|
|
|
|
|
|
|
| |
simplify the logic of initializing function parameters so that we don't need
both a variable declaration and a type in FunctionArgList. This also means
that we need to propagate the CGFunctionInfo down in a lot of places rather
than recalculating it from the FAL. There's more we can do to eliminate
redundancy here, and I've left FIXMEs behind to do it.
llvm-svn: 127314
|
| |
|
|
|
|
| |
This reverts commit 126863.
llvm-svn: 126886
|
| |
|
|
|
|
| |
This reverts commit 126865.
llvm-svn: 126876
|
| |
|
|
| |
llvm-svn: 126865
|
| |
|
|
| |
llvm-svn: 126863
|