Lines Matching refs:vtable

9 valid vtable or function pointer for a given class or function type, and its
73 virtual table object is stored in the object's vtable pointer.  In ABI parlance
75 B is constructed, the address of ``&B::f`` is stored in the vtable pointer. In
76 this way, the vtable in B's virtual table object is compatible with A's vtable.
79 virtual table object contains two vtables, one compatible with A's vtable and
80 the other compatible with C's vtable. Objects of type D contain two virtual
82 the vtable compatible with A's vtable, and the other belonging to the C
83 subobject and containing the address of the vtable compatible with C's vtable.
87 address point within that class's vtable and the name of one of the classes
104 each vtable. For example, these type metadata entries encode the compatibility
131 .. _address point: https://itanium-cxx-abi.github.io/cxx-abi/abi.html#vtable-general
233 whether another translation unit could introduce more calls through the vtable.
234 This is not the same as the linkage of the vtable, because call sites could be
253 load from the vtable for ``B`` (using the object pointer), and then call
254 ``B::f``. This means we can't remove the function pointer from ``B``'s vtable,
260 attached to vtable objects, with the following values:
271            Virtual function calls using this vtable could be made from external
276            All virtual function calls which might use this vtable are in the
282            All virtual function calls which might use this vtable are in the
285 In addition, all function pointer loads from a vtable marked with the
289 Other parts of the vtable (RTTI, offset-to-top, ...) can still be accessed with