From: Nathan Sidwell <nathan@codesourcery.com>
To: "Ramadass, Ramanathan" <Ramanathan.Ramadass@spirentcom.com>
Cc: Jon Watson <j-watson@airvananet.com>, gcc-help@gcc.gnu.org
Subject: Re: Question about duplicate C++ functions generated with GNU 3.4.1
Date: Wed, 24 Nov 2004 14:55:00 -0000 [thread overview]
Message-ID: <41A4A0E3.1080202@codesourcery.com> (raw)
In-Reply-To: <9E9C7F94BFE2AA469B2D3B9C7AC36358041E39@bighorn.adtech-inc.com>
Ramadass, Ramanathan wrote:
>>It is to do with ctors-for-most-derived and ctors-for-base.
>
>
> Could you please elaborate on this? I too have been trying to understand
> why two copies of ctors are getting created but could never find any
> explanation. As you suggested, i browsed through the ABI but still
> haven't found anything(so far). From your remark;
http://www.codesourcery.com/cxx-abi/abi.html#vtable-ctor
and http://www.codesourcery.com/cxx-abi/abi.html#obj-ctor
talks about it, but probably not in the most enlightening terms.
> Can i infer that it has to do with the initialization of the pointer to
> the virtual base class in a derived object? Somewhere in lippman's
> "Inside the C++ object model" i had read that the ctor inits this
> pointer. Not sure that it is related. Would appreciate it if you(or
> somebody else) could throw some light on this.
that presumes a particular ABI implementation, which is now incorrect for
g++ However the basic idea is the same.
nathan
--
Nathan Sidwell :: http://www.codesourcery.com :: CodeSourcery LLC
nathan@codesourcery.com :: http://www.planetfall.pwp.blueyonder.co.uk
next prev parent reply other threads:[~2004-11-24 14:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-24 3:05 Ramadass, Ramanathan
2004-11-24 14:55 ` Nathan Sidwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-11-23 13:07 Eljay Love-Jensen
2004-11-22 21:11 Jon Watson
2004-11-23 15:40 ` Nathan Sidwell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41A4A0E3.1080202@codesourcery.com \
--to=nathan@codesourcery.com \
--cc=Ramanathan.Ramadass@spirentcom.com \
--cc=gcc-help@gcc.gnu.org \
--cc=j-watson@airvananet.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).