From: Daniel Jacobowitz <drow@mvista.com>
To: Michael Elizabeth Chastain <mec.gnu@mindspring.com>
Cc: carlton@kealia.com, gdb-patches@sources.redhat.com
Subject: Re: [rfa/c++] cp_lookup_rtti_type, take 2
Date: Fri, 05 Dec 2003 05:01:00 -0000 [thread overview]
Message-ID: <20031205050118.GA15159@nevyn.them.org> (raw)
In-Reply-To: <20031205042237.56AFD4B35C@berman.michael-chastain.com>
On Thu, Dec 04, 2003 at 11:22:37PM -0500, Michael Chastain wrote:
> Cool, I will commit this patch now.
>
> > The only reason we can do it by symbol lookup at all is the One
> > Definition Rule, and we should probably be restricting ourselves to the
> > objfile in which we found the minimal symbol.
>
> Yes, it's still very flaky. The only reason it works now is that
> there is a low-priority "fallback" search over all static blocks.
> That is just more trouble waiting to happen.
Trouble doesn't generally happen, though, because of the ODR.
> We've got a vtbl pointer, and we want type information for it.
> So we translate:
>
> vtbl address -> minsym
> minsym -> mangled name
> mangled name -> demangled name
> demangled name -> prefix
> prefix -> symbol
> symbol -> type
>
> Maybe we should just go from the vtbl address to the symbol without
> converting to a name and back again?!
We don't have any information to do that, unless you know something I
don't.
> > Now that we've had another major release of GDB I am extremely tempted
> > to rip out aCC C++ support. If you really want to experiment, the HP
> > TestDrive systems do have aCC installed; www.testdrive.hp.com and
> > spe191.testdrive.hp.com:telnet. But they're a real nuisance to run
> > tests on due to the lack of usable (to me) tools, and the restrictive
> > firewall.
>
> That's in my area. "Get into testdrive" is a task for me, and "set up
> migchain/migbat" is another task. I can handle the lack of tools as
> long as there is lots of disk space, because I bootstrap the whole
> toolchain. I'll have to see how restrictive the firewall is.
You may have to start bootstrap a little further back than usual.
You'll need at least GNU Make... HP-UX's make is incredibly annoying.
> > And if we found problems, there wouldn't be anyone motivated
> > to fix them.
>
> Well, it would be useful to get enough hpux running to clean up
> all the hp/acc special code in the test suite. It would be great
> if acc is completely getting replaced, too.
>
> > The "earlier version" used VAR_DOMAIN, FYI. It was presumably based on
> > the code in gnu-v2-abi.c, but because gnu-v2-abi.c didn't show the
> > problem I encountered at the time I didn't update it.
>
> Aha, the history is falling into place.
>
> In retrospect, my new lookup_rtti_type should take the domain as a parameter.
I don't really think so. You're always (?) looking for aggregate types
STRUCT_DOMAIN is the most useful place to find them.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-12-05 5:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-05 4:23 Michael Elizabeth Chastain
2003-12-05 5:01 ` Daniel Jacobowitz [this message]
2003-12-05 17:12 ` David Carlton
2003-12-05 17:16 ` Daniel Jacobowitz
2003-12-05 17:38 ` David Carlton
2003-12-05 17:40 ` Daniel Jacobowitz
-- strict thread matches above, loose matches on Subject: below --
2003-12-05 5:26 Michael Elizabeth Chastain
2003-12-01 21:40 Michael Elizabeth Chastain
2003-12-05 3:30 ` Daniel Jacobowitz
2003-12-05 16:57 ` David Carlton
2003-12-05 17:16 ` 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=20031205050118.GA15159@nevyn.them.org \
--to=drow@mvista.com \
--cc=carlton@kealia.com \
--cc=gdb-patches@sources.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