From: Tom Tromey <tom@tromey.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Allow DW_ATE_UTF for Rust characters
Date: Wed, 10 Nov 2021 12:57:41 -0700 [thread overview]
Message-ID: <877ddfhjgq.fsf@tromey.com> (raw)
In-Reply-To: <20211031171744.1746609-1-tom@tromey.com> (Tom Tromey's message of "Sun, 31 Oct 2021 11:17:44 -0600")
>>>>> "Tom" == Tom Tromey <tom@tromey.com> writes:
Tom> The Rust compiler plans to change the encoding of a Rust 'char' type
Tom> to use DW_ATE_UTF. You can see the discussion here:
Tom> https://github.com/rust-lang/rust/pull/89887
[...]
I plan to land this relatively soon, but I wanted to note that I would
also like to backport this to gdb 11. The Rust compiler developers are
discussing whether to land this change to the compiler, and I think it
would be helpful if a fix were in the next gdb release. I will file a
bugzilla ticket for this, per protocol; please take a look at the patch
and let me know what you think.
Tom
next prev parent reply other threads:[~2021-11-10 19:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-31 17:17 Tom Tromey
2021-11-10 19:57 ` Tom Tromey [this message]
2021-11-21 13:33 ` Joel Brobecker
2021-11-29 18:04 ` Tom Tromey
2021-12-04 11:23 ` Joel Brobecker
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=877ddfhjgq.fsf@tromey.com \
--to=tom@tromey.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).