From: David Carlton <carlton@kealia.com>
To: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
Cc: dan@debian.org, ezannoni@redhat.com,
gdb-patches@sources.redhat.com, jimb@redhat.com
Subject: Re: [rfa/symtab/c++] fix c++ rtti type lookup
Date: Mon, 01 Dec 2003 17:13:00 -0000 [thread overview]
Message-ID: <yf27k1go401.fsf@hawaii.kealia.com> (raw)
In-Reply-To: <20031127070903.48F634B40B@berman.michael-chastain.com> (Michael Elizabeth Chastain's message of "Thu, 27 Nov 2003 02:09:03 -0500 (EST)")
On Thu, 27 Nov 2003 02:09:03 -0500 (EST), mec.gnu@mindspring.com (Michael Elizabeth Chastain) said:
> This patch is a partial fix for PR c++/1465, which is the bug where
> RTTI lookup gets the "namespace" symbol instead of the class symbol.
Thanks; I can't recommend this for approval, but it basically looks
good to me. A few quibbles:
> I think I need approval from a symtab maintainer to add the new
> utility function "lookup_rtti_type", and then approval from a C++
> maintainer to change gnuv2_rtti_type and gnuv3_rtti_type to call
> lookup_rtti_type.
Just C++ approval is fine - it's not in symtab.c, and we have other
C++-specific symbol-lookup code that was moved out of symtab.c exactly
so that it wouldn't require symtab approval. Though I would put the
new function in cp-namespace.c/cp-support.h, until we decide to create
a cp-symtab.c, because that's where the other C++-specific symtab
stuff currently is.
> + if (SYMBOL_CLASS (rtti_sym) != LOC_TYPEDEF)
> + {
> + warning ("RTTI symbol for class '%s' is not a typedef", name);
I would change this to 'is not a type' - we put them in something
called LOC_TYPEDEF, but users would expect 'typedef' to refer to the
C/C++ meaning of the term.
David Carlton
carlton@kealia.com
next prev parent reply other threads:[~2003-12-01 17:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-27 7:09 Michael Elizabeth Chastain
2003-12-01 17:13 ` David Carlton [this message]
2003-12-04 21:16 ` Elena Zannoni
2003-12-04 21:18 ` David Carlton
2003-12-04 21:38 Michael Elizabeth Chastain
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=yf27k1go401.fsf@hawaii.kealia.com \
--to=carlton@kealia.com \
--cc=dan@debian.org \
--cc=ezannoni@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@redhat.com \
--cc=mec.gnu@mindspring.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