public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Thomas Schwinge <tschwinge@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc/devel/rust/master] Merge #1651
Date: Thu,  1 Dec 2022 08:12:21 +0000 (GMT)	[thread overview]
Message-ID: <20221201081221.DB33E3858408@sourceware.org> (raw)

https://gcc.gnu.org/g:71b8beb150d96548a2ebfb8ef964d14225e300f0

commit 71b8beb150d96548a2ebfb8ef964d14225e300f0
Merge: 9ef8144e399 b43c5d4fd82
Author: bors[bot] <26634292+bors[bot]@users.noreply.github.com>
Date:   Mon Nov 28 11:45:44 2022 +0000

    Merge #1651
    
    1651: Improve dump lex r=CohenArthur a=tamaroning
    
    Fixes #1650
    
    
    Co-authored-by: Raiki Tamura <tamaron1203@gmail.com>

Diff:

 gcc/rust/lex/rust-lex.cc         | 47 +++++++++++++++++++++++++++++++++++++---
 gcc/rust/lex/rust-lex.h          | 12 ++++++++--
 gcc/rust/parse/rust-parse-impl.h | 41 -----------------------------------
 gcc/rust/parse/rust-parse.h      |  2 --
 gcc/rust/rust-session-manager.cc | 41 +++++++++++++++--------------------
 gcc/rust/util/rust-optional.h    |  1 +
 6 files changed, 72 insertions(+), 72 deletions(-)

                 reply	other threads:[~2022-12-01  8:12 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20221201081221.DB33E3858408@sourceware.org \
    --to=tschwinge@gcc.gnu.org \
    --cc=gcc-cvs@gcc.gnu.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).