public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bgreen at nas dot nasa dot gov" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/11247] -frepo fails to instantiate typeinfo
Date: Tue, 02 Sep 2003 20:14:00 -0000	[thread overview]
Message-ID: <20030902201402.21531.qmail@sources.redhat.com> (raw)
In-Reply-To: <20030618234434.11247.bgreen@nas.nasa.gov>

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11247



------- Additional Comments From bgreen at nas dot nasa dot gov  2003-09-02 20:14 -------
I have uncovered what appears to be the cause for this bug.  I hope this is
helpful in some way.

When the compiler processes the dynamic_cast, the repo code emits the following
into the .rpo file:

O _ZTV5ITypeIiE

running c++filt on this shows that this refers to the class's vtable:

O vtable for IType<int>

However, the linker (run via collect2) produces an error indicating a missing
'typeinfo', but not a missing 'vtable':

GNU ld version 2.14 20030612
test.o(.text+0x32): In function `main':
/home/bgreen/code/tests/comcasts/tex3/test.C:23: undefined reference to
`typeinfo for IType<int>'

collect2 is then unable to match the unresolved typeinfo to the uninstantiated
vtable.
It seems that the problem boils down to the compiler repo code emitting a
'vtable' where it should emit a 'typeinfo' in response to a dynamic cast.


  parent reply	other threads:[~2003-09-02 20:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-18 23:44 [Bug c++/11247] New: " bgreen at nas dot nasa dot gov
2003-06-19 13:47 ` [Bug c++/11247] " bangerth at dealii dot org
2003-07-29 16:33 ` pinskia at physics dot uc dot edu
2003-09-02 20:14 ` bgreen at nas dot nasa dot gov [this message]
2004-08-16 18:25 ` bangerth at dealii dot org
2004-08-25 17:02 ` pinskia at gcc dot gnu dot org
2004-12-31  0:14 ` bgreen at nas dot nasa dot gov
2005-01-31  6:57 ` pinskia at gcc dot gnu dot org
     [not found] <bug-11247-1825@http.gcc.gnu.org/bugzilla/>
2007-06-14 22:32 ` aaw at gcc dot gnu dot 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=20030902201402.21531.qmail@sources.redhat.com \
    --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).