From: Daniel Berlin <dberlin@redhat.com>
To: Michael Elizabeth Chastain <chastain@cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Start abstraction of C++ abi's
Date: Sun, 18 Feb 2001 16:51:00 -0000 [thread overview]
Message-ID: <x7y9v34hrk.fsf@dynamic-addr-83-177.resnet.rochester.edu> (raw)
In-Reply-To: <200102190009.QAA20605@bosch.cygnus.com>
Michael Elizabeth Chastain <chastain@cygnus.com> writes:
> Looks like a good idea to me. "set demangle" currently shows five
> different styles (gnu, lucid, arm, hp, edg). We know that gnu encompasses
> two different manglers by itself. We gotta move these things into
> virtual functions.
Well, actually, we only support 2 C++ abi's right now (4 if you really
want to try to call cfront an ABI), HP, GNUv2.
We can demangle functions for lucid/arm/edg, but we can't actually do
anything advanced with programs using those abi's (if they exist),
like virtual function calling/virtual base searching/etc.
>
> I won't comment on the directory structure (cp/cp-abi versus cp-abi);
> maybe a maintainer would like to think about that.
>
> Some specific comments:
>
> > ! constructor_prefix_p (physname)
> > ! || destructor_prefix_p (physname)
> > ! || STREQN (method_name, "~", 1);
>
> Does that lingering STREQN have to be there?
I can make it strncmp, or just check method_name[1], but it doesn't
make sense otherwise. It's just seeing if the first letter is a "~" in
the actual demangled method name, rather than the mangled name.
>
> > demangled_name =
> > cplus_demangle (mangled_name,
> > ! DMGL_ANSI | DMGL_PARAMS | DMGL_VERBOSE);
>
> This looks like you mixed in a bit from a different patch -- there is no
> DMGL_VERBOSE in the gdb cvs tree yet.
Yup. It's from the demangle changes I haven't gotten approved yet.
I'll cut it out.
>
> Beyond that I haven't proof-read the code yet.
>
> Michael
next prev parent reply other threads:[~2001-02-18 16:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-18 16:09 Michael Elizabeth Chastain
2001-02-18 16:51 ` Daniel Berlin [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-02-19 15:08 Michael Elizabeth Chastain
[not found] <200102192211.OAA18590@bosch.cygnus.com>
2001-02-19 14:32 ` Andrew Cagney
2001-02-19 15:01 ` Daniel Berlin
2001-02-18 16:58 Michael Elizabeth Chastain
2001-02-18 18:05 ` Daniel Berlin
2001-02-18 12:51 Daniel Berlin
2001-02-18 22:52 ` Eli Zaretskii
2001-02-19 0:02 ` Daniel Berlin
2001-02-19 3:06 ` Eli Zaretskii
2001-02-19 6:32 ` Daniel Berlin
2001-02-19 8:48 ` Elena Zannoni
2001-02-19 10:24 ` Daniel Berlin
2001-02-19 11:27 ` Andrew Cagney
2001-02-19 13:17 ` Daniel Berlin
2001-02-19 13:36 ` Andrew Cagney
2001-02-19 14:58 ` Stan Shebs
2001-02-19 15:13 ` Michael Snyder
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=x7y9v34hrk.fsf@dynamic-addr-83-177.resnet.rochester.edu \
--to=dberlin@redhat.com \
--cc=chastain@cygnus.com \
--cc=gdb-patches@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