From: David Edelsohn <dje@watson.ibm.com>
To: Robert Boehne <rboehne@ricardo-us.com>
Cc: gcc@gcc.gnu.org
Subject: Re: AIX g++ 3.0.2 Undefined symbol: virtual thunk to...
Date: Thu, 06 Dec 2001 09:55:00 -0000 [thread overview]
Message-ID: <200112061744.MAA26192@makai.watson.ibm.com> (raw)
In-Reply-To: Message from Robert Boehne <rboehne@ricardo-us.com> of "Thu, 06 Dec 2001 11:20:26 CST." <3C0FA8DA.945EEA50@ricardo-us.com>
>>>>> Robert Boehne writes:
Robert> Now I'm baffled. If g++ isn't generating them, how do they get
Robert> into my object code? Doing an nm of this library I get 68 lines
Robert> that match "thunk".
Robert> nm ./sigc++/.libs/libsigc.a | c++filt | grep thunk
Robert> 000000001004b668 t .non-virtual thunk to std::iostream::~iostream()
Robert> <SNIP>
Robert> 0000000020010e48 d virtual thunk to std::strstream::~strstream()
Robert> 0000000020010ca4 d virtual thunk to SigC::Object::~Object()
Robert> 0000000020010c98 d virtual thunk to
Robert> SigC::Object::~Object()
Robert> Are you saying that some other compiler is generating these?
Robert> My suspicion is that it is related to having a compiler configured
Robert> with "--disable-shared --disable-threads" so I'm working on
Robert> re-bootstrapping gcc with "--enable-threads=posix --enable-shared".
Robert> I'm not sure what a "thunk" is so the link error doesn't help
Robert> me much.
I do not know what a virtual thunk is.
Thunks are described on many websites. It is a piece of code to
fix up the "this" pointer for multiple inheritance.
Maybe some part of GCC is not obeying #ifdef ASM_OUTPUT_MI_THUNK.
David
next prev parent reply other threads:[~2001-12-06 17:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-04 12:59 Robert Boehne
2001-12-04 13:03 ` David Edelsohn
2001-12-06 9:20 ` Robert Boehne
2001-12-06 9:55 ` David Edelsohn [this message]
2001-12-06 11:18 ` PR4122 Regression from 2.95 in 3.0.2 (Was: Re: AIX g++ 3.0.2 Undefined symbol: virtual thunk to...) Robert Boehne
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=200112061744.MAA26192@makai.watson.ibm.com \
--to=dje@watson.ibm.com \
--cc=gcc@gcc.gnu.org \
--cc=rboehne@ricardo-us.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).