public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
* [Bug rust/20166] utf-8 input not handled by rust lexer
[not found] <bug-20166-4717@http.sourceware.org/bugzilla/>
@ 2022-01-26 22:50 ` tromey at sourceware dot org
2022-02-06 20:39 ` cvs-commit at gcc dot gnu.org
2022-02-06 21:19 ` tromey at sourceware dot org
2 siblings, 0 replies; 3+ messages in thread
From: tromey at sourceware dot org @ 2022-01-26 22:50 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=20166
Tom Tromey <tromey at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|unassigned at sourceware dot org |tromey at sourceware dot org
--- Comment #1 from Tom Tromey <tromey at sourceware dot org> ---
I have a patch.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug rust/20166] utf-8 input not handled by rust lexer
[not found] <bug-20166-4717@http.sourceware.org/bugzilla/>
2022-01-26 22:50 ` [Bug rust/20166] utf-8 input not handled by rust lexer tromey at sourceware dot org
@ 2022-02-06 20:39 ` cvs-commit at gcc dot gnu.org
2022-02-06 21:19 ` tromey at sourceware dot org
2 siblings, 0 replies; 3+ messages in thread
From: cvs-commit at gcc dot gnu.org @ 2022-02-06 20:39 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=20166
--- Comment #2 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tom Tromey <tromey@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=a723766c0e2cc4e8d53813f90f1167e620da0784
commit a723766c0e2cc4e8d53813f90f1167e620da0784
Author: Tom Tromey <tom@tromey.com>
Date: Wed Jan 26 15:39:03 2022 -0700
Allow non-ASCII characters in Rust identifiers
Rust 1.53 (quite a while ago now) ungated the support for non-ASCII
identifiers. This didn't work in gdb. This is PR rust/20166.
This patch fixes the problem by allowing non-ASCII characters to be
considered as identifier components. It seemed simplest to just pass
them through -- doing any extra checking didn't seem worthwhile.
The new test also verifies that such characters are allowed in strings
and character literals as well. The latter also required a bit of
work in the lexer.
Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=20166
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug rust/20166] utf-8 input not handled by rust lexer
[not found] <bug-20166-4717@http.sourceware.org/bugzilla/>
2022-01-26 22:50 ` [Bug rust/20166] utf-8 input not handled by rust lexer tromey at sourceware dot org
2022-02-06 20:39 ` cvs-commit at gcc dot gnu.org
@ 2022-02-06 21:19 ` tromey at sourceware dot org
2 siblings, 0 replies; 3+ messages in thread
From: tromey at sourceware dot org @ 2022-02-06 21:19 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=20166
Tom Tromey <tromey at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |11.2
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #3 from Tom Tromey <tromey at sourceware dot org> ---
Fixed.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2022-02-06 21:19 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <bug-20166-4717@http.sourceware.org/bugzilla/>
2022-01-26 22:50 ` [Bug rust/20166] utf-8 input not handled by rust lexer tromey at sourceware dot org
2022-02-06 20:39 ` cvs-commit at gcc dot gnu.org
2022-02-06 21:19 ` tromey at sourceware dot org
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).