From: Amanieu d'Antras via Gdb-patches <gdb-patches@sourceware.org>
To: gdb-patches@sourceware.org
Subject: [gcc-10-branch] libiberty: Support the new ("v0") mangling scheme in rust-demangle
Date: Tue, 12 Jan 2021 19:36:09 +0000 [thread overview]
Message-ID: <CA+y5pbTWSeJX_yCywHsU80m5uGVptekedVH7OGvq7pQH19Ld=g@mail.gmail.com> (raw)
Rust is in the process of migrating to a new symbol mangling scheme called "v0".
Details can be found in the tracking issue:
https://github.com/rust-lang/rust/issues/60705
Demangler support for v0 has already been upstreamed in GCC's libiberty and is
available in gdb-binutils master. However we would like the demangler to be
backported to GDB 10 so that debugging experience does not regress when we
switch to generating v0 symbol names by default.
The specific GCC commit that contains the v0 Rust demangler is:
commit 84096498a7bd788599d4a7ca63543fc7c297645e
libiberty: Support the new ("v0") mangling scheme in rust-demangle
The patch applies cleanly to gdb-10-branch.
next reply other threads:[~2021-01-12 19:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-12 19:36 Amanieu d'Antras via Gdb-patches [this message]
2021-01-13 1:02 ` Tom Tromey
2021-01-13 1:08 ` Simon Marchi via Gdb-patches
2021-01-13 1:49 ` Amanieu d'Antras via Gdb-patches
2021-01-13 3:18 ` Tom Tromey
2021-01-16 17:29 ` Tom Tromey
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='CA+y5pbTWSeJX_yCywHsU80m5uGVptekedVH7OGvq7pQH19Ld=g@mail.gmail.com' \
--to=gdb-patches@sourceware.org \
--cc=amanieu@gmail.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