public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug rust/21185] add i128 and u128 support to rust lexer and parser
Date: Wed, 01 Mar 2023 21:51:13 +0000 [thread overview]
Message-ID: <bug-21185-4717-2jtMSClNb8@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-21185-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=21185
Tom Tromey <tromey at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|DUPLICATE |---
Depends on|20991 |
Blocks| |20991
Status|RESOLVED |REOPENED
Summary|add i128 and u128 support |add i128 and u128 support
|to rust |to rust lexer and parser
--- Comment #14 from Tom Tromey <tromey at sourceware dot org> ---
Un-duping and repurposing again as the rust lexer / parser
part of 128-bit ints.
Referenced Bugs:
https://sourceware.org/bugzilla/show_bug.cgi?id=20991
[Bug 20991] __int128 type support
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-03-01 21:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-21185-4717@http.sourceware.org/bugzilla/>
2023-02-23 16:37 ` [Bug rust/21185] add i128 and u128 support to rust tromey at sourceware dot org
2023-03-01 21:51 ` tromey at sourceware dot org [this message]
2023-03-27 20:28 ` [Bug rust/21185] add i128 and u128 support to rust lexer and parser tromey at sourceware dot org
2023-03-28 16:02 ` tromey at sourceware dot org
2023-04-17 17:03 ` cvs-commit at gcc dot gnu.org
2023-04-17 17:05 ` tromey at sourceware dot org
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=bug-21185-4717-2jtMSClNb8@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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).