From: Daniel Jacobowitz <dan@codesourcery.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Chris Moller <cmoller@redhat.com>, gdb-patches@sourceware.org
Subject: Re: beta patch for PR 9065
Date: Tue, 16 Feb 2010 22:57:00 -0000 [thread overview]
Message-ID: <20100216225702.GA9914@caradoc.them.org> (raw)
In-Reply-To: <m31vgkizoc.fsf@fleche.redhat.com>
On Tue, Feb 16, 2010 at 03:27:47PM -0700, Tom Tromey wrote:
> >>>>> "Daniel" == Daniel Jacobowitz <dan@codesourcery.com> writes:
>
> Daniel> It's been a while since I looked at this, but the typeinfo for a class
> Daniel> with RTTI should be available in the symbol table (_ZTI
> Daniel> symbols).
>
> Oh, right. Maybe I was confusing this w/ a vtable slot, whoops.
It's both, but there are also _ZTI symbols for things without vtables;
e.g. standard types ("int") and classes without a vtable but where
typeid was used. The vtable's probably preferable where available.
> Daniel> We could synthesize a type_info object; the Itanium C++ ABI defines
> Daniel> the layout (section 2.9.5). But we might also have to synthesize its
> Daniel> name() method, as it is unlikely to be emitted out of line.
>
> I think it would be acceptable, though not ideal, to give an error in
> this situation.
Yes - it's a more general problem - IMO it'd be nice to be able to
have scripts implement not-outlined methods. std::string.length() is
probably similar...
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2010-02-16 22:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-16 18:31 Chris Moller
2010-02-16 21:53 ` Daniel Jacobowitz
2010-02-16 22:02 ` Chris Moller
2010-02-16 22:27 ` Tom Tromey
2010-02-16 22:57 ` Daniel Jacobowitz [this message]
2010-02-16 22:25 ` Tom Tromey
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=20100216225702.GA9914@caradoc.them.org \
--to=dan@codesourcery.com \
--cc=cmoller@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@redhat.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