Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Amanieu d'Antras via Gdb-patches <gdb-patches@sourceware.org>
Cc: Amanieu d'Antras <amanieu@gmail.com>
Subject: Re: [gcc-10-branch] libiberty: Support the new ("v0") mangling scheme in rust-demangle
Date: Tue, 12 Jan 2021 18:02:01 -0700	[thread overview]
Message-ID: <87k0shbqeu.fsf@tromey.com> (raw)
In-Reply-To: <CA+y5pbTWSeJX_yCywHsU80m5uGVptekedVH7OGvq7pQH19Ld=g@mail.gmail.com> (Amanieu d'Antras via Gdb-patches's message of "Tue, 12 Jan 2021 19:36:09 +0000")

Amanieu> Demangler support for v0 has already been upstreamed in GCC's libiberty and is
Amanieu> available in gdb-binutils master. However we would like the demangler to be
Amanieu> backported to GDB 10 so that debugging experience does not regress when we
Amanieu> switch to generating v0 symbol names by default.

I don't know whether we plan to do another release from the GDB 10
branch.  Maybe Joel could say.

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?

Anyway, it's fine by me to do this.  If there's no objections I can do
it sometime.  You may want to ping after a week or so in case I forget.

thanks,
Tom

  reply	other threads:[~2021-01-13  1:02 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 [this message]
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=87k0shbqeu.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=amanieu@gmail.com \
    --cc=gdb-patches@sourceware.org \
    /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