From: Amanieu d'Antras via Gdb-patches <gdb-patches@sourceware.org>
To: Tom Tromey <tom@tromey.com>
Cc: Amanieu d'Antras via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [gcc-10-branch] libiberty: Support the new ("v0") mangling scheme in rust-demangle
Date: Wed, 13 Jan 2021 01:49:59 +0000 [thread overview]
Message-ID: <CA+y5pbQgA5am4Ni=ppzydXm22z56tJ0Y9ssKYWT2J4RXhY++3w@mail.gmail.com> (raw)
In-Reply-To: <87k0shbqeu.fsf@tromey.com>
> Also, is there a way to test that this works correctly? I'd imagine
> there just has to be a flag day sometime and then we find out? Or has
> someone built Rust and tried it with GDB trunk?
rustc can already generate v0 symbols with the
-Zsymbol-mangling-version=v0 flag. We're just going to eventually be
switching this on by default.
I just tested a small program built with that flag and gdb trunk can
successfully demangle the symbols while gdb 10 can't.
next prev parent reply other threads:[~2021-01-13 1:50 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
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 [this message]
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+y5pbQgA5am4Ni=ppzydXm22z56tJ0Y9ssKYWT2J4RXhY++3w@mail.gmail.com' \
--to=gdb-patches@sourceware.org \
--cc=amanieu@gmail.com \
--cc=tom@tromey.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