Virtual base class offsets in vtables

[Jason Merrill]

>>>>> Mark Mitchell <mark at codesourcery.com> writes:

>>>>> "Jason" == Jason Merrill <jason at cygnus.com> writes:
 >>> o Furthermore, it's unclear whether or not offsets for indirect
 >>> virtual bases should be stored.  The Category 3 description
 >>> seems to indicate that only *direct* bases should be stored;
 >>> otherwise left-to-right declaration order isn't really
 >>> well-defined.  But, Category 4 clearly says direct or indirect
 >>> bases.

 Jason> The idea is to promote vbase offsets, like virtual function
 Jason> entries, out of virtual bases and not non-virtual bases.

 > I'm not sure I understand.  But, let's see if this is what we want:

 >   For a primary vtable, there is exactly one vbase offset entry for
 >   each direct and indirect virtual base class.

Not exactly; we only have entries for indirect virtual base classes that
are reached through another virtual base.

Jason