From: Tom Tromey <tom@tromey.com>
To: Keith Seitz <keiths@redhat.com>
Cc: Simon Marchi <simon.marchi@ericsson.com>,
"gdb-patches\@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] gdb: Remove support for old mangling schemes
Date: Wed, 09 Jan 2019 16:59:00 -0000 [thread overview]
Message-ID: <87zhs9py1g.fsf@tromey.com> (raw)
In-Reply-To: <e8dcdefe-5f8f-6e1b-116f-f4bf166d55c6@redhat.com> (Keith Seitz's message of "Tue, 8 Jan 2019 16:24:51 -0800")
>>>>> "Keith" == Keith Seitz <keiths@redhat.com> writes:
Keith> The manual talks about several demangling-related features which
Keith> raised questions for me about the general support for gnu-v2 code. If
Keith> libiberty is removing support for v2 demangling, how useful will GDB be
Keith> without the ability to demangle v2 symbols? Should we deprecate or remove
Keith> that, too? /me opens can of worms
I tend to think removing the GNU v2 ABI support would be fine.
It's long since obsolete. If someone out there still requires gcc 2.95,
I suppose they can either build an old gdb as well, or use "set lang c".
Tom
next prev parent reply other threads:[~2019-01-09 16:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-08 23:22 Simon Marchi
2019-01-09 3:38 ` Eli Zaretskii
2019-01-09 4:12 ` Simon Marchi
2019-01-09 16:54 ` Tom Tromey
[not found] ` <e8dcdefe-5f8f-6e1b-116f-f4bf166d55c6@redhat.com>
2019-01-09 4:36 ` Simon Marchi
2019-01-09 16:59 ` Tom Tromey [this message]
2019-01-09 18:53 ` Pedro Alves
2019-01-09 4:50 ` [PATCH v2] " Simon Marchi
[not found] ` <83h8ehj0wi.fsf@gnu.org>
2019-01-09 15:59 ` Simon Marchi
2019-01-09 16:14 ` Eli Zaretskii
2019-01-09 16:18 ` Simon Marchi
2019-01-09 17:02 ` Keith Seitz
2019-01-09 18:08 ` Simon Marchi
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=87zhs9py1g.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=keiths@redhat.com \
--cc=simon.marchi@ericsson.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