Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Per Bothner <per@bothner.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: patch to robustify gnuv3_rtti_type
Date: Sat, 19 Jan 2002 16:19:00 -0000	[thread overview]
Message-ID: <20020119192000.A1028@nevyn.them.org> (raw)
In-Reply-To: <3C4A0C1F.6070903@bothner.com>

On Sat, Jan 19, 2002 at 04:15:27PM -0800, Per Bothner wrote:
> Daniel Jacobowitz wrote:
> >>	* gnu-v3-abi.c (gnuv3_rtti_type):  Guard that vtable_symbol_name
> >>	isn't NULL, which can happen with some gcj3.0-produced code.
> >
> >OK for now.
> 
> I checked it in.
> 
> >I'll see if we can cope with the vtables that it currently
> >emits, too.
> 
> Well, I have a non-checked-in gcj path that is one step towards
> fixing the vtables, in that it add sthe extra header words "in
> front of" the vtable pointer.  I.e. I've allocated space in
> the vtable for the rtti pointer, though leaving the pointer
> null.  The next step is sctually generating the type_info
> object.  It might be nice to actually *embed* the type_info
> object inside the Class object, possibly reducing some
> duplication.

Go look at gnuv3_rtti_type again.  It's misnamed; it does not use RTTI
at all.  It only looks that the vtable exists and has a name demangled to
'vtable for <Class>'.

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2002-01-20  0:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-19 12:40 Per Bothner
2002-01-19 15:38 ` Daniel Jacobowitz
2002-01-19 16:15   ` Per Bothner
2002-01-19 16:19     ` Daniel Jacobowitz [this message]
2002-01-20 12:43       ` Per Bothner
2002-01-20 12:54         ` Daniel Jacobowitz
2002-01-20 16:00           ` Per Bothner
2002-01-20 14:24         ` Daniel Berlin
2002-01-19 17:50 ` Daniel Jacobowitz

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=20020119192000.A1028@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=per@bothner.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