From: Daniel Berlin <dan@cgsoftware.com>
To: Jason Merrill <jason@redhat.com>
Cc: Michael Elizabeth Chastain <mec@shout.net>,
<gdb-patches@sources.redhat.com>, <gcc@gcc.gnu.org>
Subject: Re: [RFA/stabs reader] Fix v3 duplicate constructors problem
Date: Tue, 04 Dec 2001 07:40:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.33.0112041038150.5755-100000@www.cgsoftware.com> (raw)
In-Reply-To: <wvl7ks3ce08.fsf@prospero.cambridge.redhat.com>
On Tue, 4 Dec 2001, Jason Merrill wrote:
> >>>>> "Michael" == Michael Elizabeth Chastain <mec@shout.net> writes:
>
> > I would like gdb to demangle different names differently.
>
> Which brings me to a question: Why don't we demangle them differently?
> Currently, flag_verbose in cp-demangle.c defaults to 0, so the two
> functions are demangled identically. I think this is wrong, and have
> changed flag_verbose to 1 for my own use. What do other people think?
IIRC, the reason was that ptype output should be directly usable in the
target language.
We had a large discussion about this sometime in the past year, i can't
quite remember the outcome.
I had a patch to gdb/libiberty that passed DMGL_VERBOSE along (and added
DMGL_VERBOSE to the flags) for this purpose.
>
> Jason
>
next prev parent reply other threads:[~2001-12-04 15:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-04 1:09 Michael Elizabeth Chastain
2001-12-04 5:27 ` Jason Merrill
2001-12-04 7:40 ` Daniel Berlin [this message]
2001-12-04 8:58 ` Daniel Jacobowitz
[not found] <20011203154836.A28821@nevyn.them.org>
2001-12-03 13:52 ` Jason Merrill
2001-12-03 14:29 ` Daniel Jacobowitz
2001-12-03 14:58 ` Jason Merrill
2001-12-03 15:25 ` Michael Snyder
2001-12-04 8:25 ` Jason Merrill
2001-12-04 8:53 ` Jim Blandy
2001-12-04 9:43 ` Joe Buck
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=Pine.LNX.4.33.0112041038150.5755-100000@www.cgsoftware.com \
--to=dan@cgsoftware.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=jason@redhat.com \
--cc=mec@shout.net \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).