forked from OSchip/llvm-project
dd72aafffc
Go through and expand the members of bases into the encoding string (and encode the VTable as well). Unlike gcc which expands virtual bases as many times as they appear in the hierarchy, clang will only expand them once at the end, to reflect the actual layout. Note that there doesn't seem to be a way to indicate in the encoding that packing/alignment of members is different that normal, in which case the encoding will be out-of-sync with the real layout. If the runtime switches to just consider the size of types without taking into account alignment, we could easily make padding explicit in the encoding (e.g. using arrays of chars). The encoding strings would be longer then though. Also encode a flexible array member as array of 0 size, like gcc, not as a pointer. llvm-svn: 131365 |
||
|---|---|---|
| .. | ||
| block-in-template-inst.mm | ||
| block-var-layout.mm | ||
| blocks.mm | ||
| copyable-property-object.mm | ||
| encode.mm | ||
| exceptions.mm | ||
| foreach-statement.mm | ||
| implicit-copy-assign-operator.mm | ||
| implicit-copy-constructor.mm | ||
| ivar-objects.mm | ||
| mangle-blocks.mm | ||
| mangle.mm | ||
| message-reference.mm | ||
| method-local-extern-mangle.mm | ||
| property-derived-to-base-conv.mm | ||
| property-dot-copy.mm | ||
| property-dot-reference.mm | ||
| property-object-conditional-exp.mm | ||
| property-objects.mm | ||
| property-reference.mm | ||
| refence-assign-write-barrier.mm | ||
| references.mm | ||
| rtti.mm | ||
| selector-expr-lvalue.mm | ||
| write-barrier-global-assign.mm | ||