of the block descriptor field.  This field is the ObjC style @encode
signature of the implementation function, and was to this point
conditionally provided in the block literal data structure.  That
provisional support is removed.

Additionally, eliminate unused enumerations for the block literal flags field.
The first shipping ABI unconditionally set (1<<29) but this bit is unused
by the runtime, so the second ABI will unconditionally have (1<<30) set so
that the runtime can in fact distinguish whether the additional data is
present or not.

llvm-svn: 96989

llvm-svn: 96962

llvm-svn: 96961

llvm-svn: 96958

llvm-svn: 96897

llvm-svn: 96883

More fixes. Don't try to emit a virtual base vtable if the virtual base in question is a primary virtual base of some other base.

llvm-svn: 96881

Always emit vcall offset for the primary base, not only if it's virtual. Remove a debug printf, and add the test case that now passes.

llvm-svn: 96880

Simplify the vcall offset calculation and make it give the correct answers :) My test case now has the right values but in the wrong order.

llvm-svn: 96877

More work on vcall offsets. We now emit the right number of vcall offsets in my local test case, but not the right values.

llvm-svn: 96874

llvm-svn: 96853

1) emit base destructors as aliases to their unique base class destructors
under some careful conditions.  This is enabled for the same targets that can
support complete-to-base aliases, i.e. not darwin.

2) Emit non-variadic complete constructors for classes with no virtual bases
as calls to the base constructor.  This is enabled on all targets and in
theory can trigger in situations that the alias optimization can't (mostly
involving virtual bases, mostly not yet supported).

These are bundled together because I didn't think it worthwhile to split them,
not because they really need to be.

llvm-svn: 96842

CLANG_VTABLE_DEBUG.

llvm-svn: 96785

since they may not have normal identifiers for names. Fixes PR6369.

llvm-svn: 96784

fixing up a few callers that thought they were propagating NoReturn
information but were in fact saying something about exception
specifications.

llvm-svn: 96766

llvm-svn: 96695

Fix some bugs with function-try-blocks and simplify normal try-block
code generation.

This implementation excludes a deleting destructor's call to
operator delete() from the function-try-block, which I believe
is correct but which I can't find straightforward support for at
a moment's glance.

llvm-svn: 96670

llvm-svn: 96660

command-line option which defaults off.

llvm-svn: 96649

instead relies on their DeclContext for iteration, etc.

llvm-svn: 96638

llvm-svn: 96635

some failure here that I can't.

llvm-svn: 96612

calling them as subroutines.  This triggers whenever the alias optimization
doesn't, i.e. when the dtor has linkonce linkage or there are virtual bases
or it's the deleting dtor.

llvm-svn: 96605

llvm-svn: 96595

llvm-svn: 96590

llvm-svn: 96587

llvm-svn: 96585

Store the base offset of the final overrider in the OverriderInfo struct, to be used for vcall offsets.

llvm-svn: 96582

llvm-svn: 96581

change.

llvm-svn: 96564

llvm-svn: 96520

a block without it being used. This causes over release
of objects in certain runtime-senitive apps.
(fixes radar 7581175).

llvm-svn: 96501

llvm-svn: 96486

llvm-svn: 96484

llvm-svn: 96481

llvm-svn: 96461

llvm-svn: 96459

llvm-svn: 96455

and destructors when the two entities are semantically identical, i.e. when
the class has no virtual base classes.  We only do this for linkage types
for which aliases are supported, i.e. internal and external, i.e. not linkonce.

llvm-svn: 96451

llvm-svn: 96449