public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: snyder@fnal.gov To: gcc-gnats@gcc.gnu.org Subject: c++/3132: Missing dtor thunk with complicated virtual derivation Date: Mon, 11 Jun 2001 17:56:00 -0000 [thread overview] Message-ID: <200106120039.f5C0dXm28008@karma.fnal.gov> (raw) >Number: 3132 >Category: c++ >Synopsis: Missing dtor thunk with complicated virtual derivation >Confidential: no >Severity: critical >Priority: medium >Responsible: unassigned >State: open >Class: wrong-code >Submitter-Id: net >Arrival-Date: Mon Jun 11 17:56:00 PDT 2001 >Closed-Date: >Last-Modified: >Originator: scott snyder >Release: 3.0 20010611 (prerelease) >Organization: >Environment: System: Linux karma 2.2.16-22 #1 Tue Aug 22 16:49:06 EDT 2000 i686 unknown Architecture: i686 host: i686-pc-linux-gnu build: i686-pc-linux-gnu target: i686-pc-linux-gnu configured with: ../egcs/configure --prefix=/usr/local/egcs --enable-threads=posix --enable-long-long >Description: If i try to compile and link the source below, i get complaints from the linker about a missing virtual thunk for ~H: [sss@karma translator]$ g++ -o xidl xidl.cpp /tmp/ccXy7K6j.o(.gnu.linkonce.d._ZTV1H+0x40): undefined reference to `virtual thunk to H::~H()' /tmp/ccXy7K6j.o(.gnu.linkonce.d._ZTV1H+0x44): undefined reference to `virtual thunk to H::~H()' collect2: ld returned 1 exit status The generated object file includes these symbols, shown here mangled and unmangled: xidl.o:00000000 W _ZTv0_n12_N1HD0Ev xidl.o:00000000 W _ZTv0_n12_N1HD1Ev xidl.o: U _ZTv0_n16_N1HD0Ev xidl.o: U _ZTv0_n16_N1HD1Ev xidl.o:00000000 W virtual thunk to H::~H() xidl.o:00000000 W virtual thunk to H::~H() xidl.o: U virtual thunk to H::~H() xidl.o: U virtual thunk to H::~H() Is this a name mangling problem? >How-To-Repeat: --------------------------------------------- struct A { int x; virtual ~A() {} }; struct B { virtual ~B() { } }; struct C { virtual ~C () {} }; struct D : public virtual A {}; struct E : virtual public B, virtual public D {}; struct F : virtual public C, virtual public E {}; struct G : public virtual E {}; struct H : public virtual F, public virtual G { virtual ~H (); }; H::~H() {} int main () { return 0; } --------------------------------------------- >Fix: >Release-Note: >Audit-Trail: >Unformatted: I have this patch from Nathan installed: 2001-06-11 Nathan Sidwell <nathan@codesourcery.com> PR c++/3089 * class.c (dfs_accumulate_vtbl_inits): Always walk down the hierarchy looking for primary bases for a ctor vtable. Recursively call oneself, if we meet our primary via this route and haven't met it yet via inheritance graph order.
next reply other threads:[~2001-06-11 17:56 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-06-11 17:56 snyder [this message] 2001-06-12 1:39 nathan 2001-06-12 11:07 nathan
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=200106120039.f5C0dXm28008@karma.fnal.gov \ --to=snyder@fnal.gov \ --cc=gcc-gnats@gcc.gnu.org \ /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: linkBe 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).