From: "Kris Warkentin" <kewarken@qnx.com>
To: "Daniel Jacobowitz" <drow@mvista.com>
Cc: <gdb@sources.redhat.com>
Subject: Re: gnu-v3-abi.c: problems w/ virtual base class
Date: Wed, 30 Oct 2002 11:19:00 -0000 [thread overview]
Message-ID: <128701c28049$34decda0$d8020c0a@catdog> (raw)
In-Reply-To: <20021030190128.GA21129@nevyn.them.org>
> OK, that's the problem. What we should probably be doing in minsyms.c
> is checking for a valid v3 mangled name...
Ah. That would probably be a fair bit of overhead to symbol loading though
if you're going to match every symbol name against some criteria. I suppose
we could optimize by never doing the check again once the abi is set to v3.
Is there an existing function to check it or should I roll my own? Also, I
didn't find any reference to gcc's mangling style in the manuals. Is it
documented or is it 'read the code'?
cheers,
Kris
next prev parent reply other threads:[~2002-10-30 19:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-30 9:10 Kris Warkentin
2002-10-30 9:20 ` Daniel Jacobowitz
2002-10-30 9:30 ` Kris Warkentin
2002-10-30 9:34 ` Daniel Jacobowitz
2002-10-30 9:46 ` Kris Warkentin
2002-10-30 10:48 ` Kris Warkentin
2002-10-30 11:00 ` Kris Warkentin
2002-10-30 11:07 ` Daniel Jacobowitz
2002-10-30 11:00 ` Daniel Jacobowitz
2002-10-30 11:19 ` Kris Warkentin [this message]
2002-10-30 11:26 ` Daniel Jacobowitz
2002-10-30 11:59 ` Kris Warkentin
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='128701c28049$34decda0$d8020c0a@catdog' \
--to=kewarken@qnx.com \
--cc=drow@mvista.com \
--cc=gdb@sources.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