This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Why don't we just FIX the damn vthunk problem?
- To: mrs at wrs dot com
- Subject: Re: Why don't we just FIX the damn vthunk problem?
- From: "Martin v. Loewis" <martin at mira dot isdn dot cs dot tu-berlin dot de>
- Date: Wed, 3 Mar 1999 09:30:59 +0100
- CC: jason at cygnus dot com, egcs at cygnus dot com, jce2 at po dot cwru dot edu
- References: <199903030315.TAA18812@kankakee.wrs.com>
> Same. Ok, I'm now confused as you what you meant. If you meant vbase
> pointers, yes, those are part of object layout, and they must be done
> before object initialization.
This is getting complicated. Yes, I was talking about vbase pointers,
as Jason suggested to use them to pass the array of vtables. They get
initialized right when the most-derived class calls all vbase
constructors. Other base classes currently find some vtable in the
vptrs of the vbases :-)
The problem I see is with mixing old and new code. If Jason's approach
is used consistently in the entire hierarchy, it'll work.
Regards,
Martin