From: Simon Marchi <simon.marchi@polymtl.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Simon Marchi <simon.marchi@ericsson.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb: Remove support for old mangling schemes
Date: Wed, 09 Jan 2019 04:12:00 -0000 [thread overview]
Message-ID: <07d8a0b070a8add802ae30ab37a780db@polymtl.ca> (raw)
In-Reply-To: <83lg3uijqd.fsf@gnu.org>
On 2019-01-08 22:38, Eli Zaretskii wrote:
>> From: Simon Marchi <simon.marchi@ericsson.com>
>> CC: Simon Marchi <simon.marchi@ericsson.com>
>> Date: Tue, 8 Jan 2019 23:22:22 +0000
>>
>> An upcoming sync with gcc's libiberty [1] will remove support for old
>> mangling schemes (GNU v2, Lucid, ARM, HP and EDG). It will remove the
>> cplus_demangle_opname function, so we need to get rid of its usages in
>> GDB (it's a GNU v2 specific function).
>
> This would mean new GDB releases will not be able to debug old
> programs, is that right? If so, perhaps we should instead keep our
> local version of the relative functions, so that GDB will not regress
> in that way. Our considerations in this matter are different from
> those of GCC.
We're talking about really old programs here. IIUC, the GNU v2 mangling
was used in the GCC 2.95 era, which is around 2002. I think it's fine
to drop support for this. If you had a system from that era, you would
have a hard time compiling today's GDB on it. And even if you just had
an old binary on a recent systems, well the older GDB releases are
always available. I don't think it's worth our time to keep
compatibility with that. Just testing it would probably be a nightmare.
I don't know much about the other mangling schemes, but I assume they
are equally ancient. Maybe somebody else can give more info about them.
Simon
next prev parent reply other threads:[~2019-01-09 4:12 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 [this message]
2019-01-09 16:54 ` Tom Tromey
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
[not found] ` <e8dcdefe-5f8f-6e1b-116f-f4bf166d55c6@redhat.com>
2019-01-09 4:36 ` [PATCH] " Simon Marchi
2019-01-09 16:59 ` Tom Tromey
2019-01-09 18:53 ` Pedro Alves
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=07d8a0b070a8add802ae30ab37a780db@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--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