public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rearnsha at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/42540] c++ error message [vtable undefined] is unhelpful
Date: Wed, 24 Feb 2010 14:17:00 -0000 [thread overview]
Message-ID: <20100224141729.7193.qmail@sourceware.org> (raw)
In-Reply-To: <bug-42540-5724@http.gcc.gnu.org/bugzilla/>
------- Comment #5 from rearnsha at gcc dot gnu dot org 2010-02-24 14:17 -------
As suggested, there's no bug in the compiler here, and the error message comes
from the linker. The linker doesn't know what the key function is, so I doubt
it could issue a more accurate diagnostic.
In fact, the key function is just a trigger to the compiler to cause it to emit
the meta-data for the class exactly once -- and because there the class could
be used in multiple compilation units it can never know which one should
contain the meta data as any of them could have done. As far as the linker is
concerned, there really is no class for A; it's the same as if there was no
definition for a global extern variable.
--
rearnsha at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |INVALID
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42540
next prev parent reply other threads:[~2010-02-24 14:17 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-29 14:44 [Bug other/42540] New: " debian-gcc at lists dot debian dot org
2009-12-29 15:06 ` [Bug other/42540] " pinskia at gcc dot gnu dot org
2009-12-29 19:27 ` pinskia at gcc dot gnu dot org
2010-01-06 10:42 ` jwakely dot gcc at gmail dot com
2010-02-24 13:26 ` manu at gcc dot gnu dot org
2010-02-24 14:17 ` rearnsha at gcc dot gnu dot org [this message]
2010-07-06 15:47 ` pinskia at gcc dot gnu dot org
2010-07-13 22:56 ` jyasskin at gmail dot com
2010-07-13 22:58 ` pinskia at gcc dot gnu dot org
2010-07-13 22:58 ` pinskia at gcc dot gnu dot org
[not found] <bug-42540-4@http.gcc.gnu.org/bugzilla/>
2011-03-17 15:41 ` manu at gcc dot gnu.org
2011-03-17 16:17 ` jyasskin at gcc dot gnu.org
2020-07-22 13:56 ` redi at gcc dot gnu.org
2020-07-22 13:57 ` redi at gcc dot gnu.org
2020-07-22 13:57 ` redi at gcc dot gnu.org
2022-03-14 14:20 ` redi at gcc dot gnu.org
2022-03-14 14:38 ` eyalroz1 at gmx dot com
2022-03-14 17:15 ` redi at gcc dot gnu.org
2022-03-14 17:22 ` redi at gcc dot gnu.org
2022-03-16 20:13 ` eyalroz1 at gmx dot com
2022-03-16 20:34 ` redi at gcc dot gnu.org
2022-03-16 20:40 ` eyalroz1 at gmx dot com
2022-07-21 21:29 ` redi at gcc dot gnu.org
2022-08-25 9:11 ` manu at gcc dot gnu.org
2022-08-25 9:17 ` manu at gcc dot gnu.org
2022-08-25 9:28 ` redi at gcc dot gnu.org
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=20100224141729.7193.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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: 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).