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 #1616 #1617
Date: Thu, 27 Oct 2022 18:56:13 +0000 (GMT)	[thread overview]
Message-ID: <20221027185613.F2955384B13A@sourceware.org> (raw)

https://gcc.gnu.org/g:353ed6ce8add32b84f0fdfbcbc020d8f7154530d

commit 353ed6ce8add32b84f0fdfbcbc020d8f7154530d
Merge: 4dbff3d0550 259c384a97f 3f3b4a45eb9
Author: bors[bot] <26634292+bors[bot]@users.noreply.github.com>
Date:   Thu Oct 27 10:49:47 2022 +0000

    Merge #1616 #1617
    
    1616: Apply 1559 master (remove system includes) r=CohenArthur a=CohenArthur
    
    Fixes #1571
    
    1617: Apply #1605 on master (fix lang spec) r=CohenArthur a=CohenArthur
    
    Co-authored-by: ibuclaw <ibuclaw@gdcproject.org>
    
    Let's still do this while we haven't resolved #1540 :)
    
    Closes #1609
    
    Co-authored-by: Arthur Cohen <arthur.cohen@embecosm.com>

Diff:

 gcc/rust/Make-lang.in               | 2 +-
 gcc/rust/ast/rust-ast-full-test.cc  | 6 +-----
 gcc/rust/ast/rust-macro.h           | 2 +-
 gcc/rust/lang-specs.h               | 4 ++--
 gcc/rust/lex/rust-codepoint.h       | 2 +-
 gcc/rust/lex/rust-lex.cc            | 5 ++---
 gcc/rust/lex/rust-token.cc          | 3 +--
 gcc/rust/lex/rust-token.h           | 7 +------
 gcc/rust/parse/rust-cfg-parser.h    | 2 --
 gcc/rust/rust-object-export.cc      | 3 +--
 gcc/rust/util/rust-attributes.cc    | 2 +-
 gcc/rust/util/rust-make-unique.h    | 2 +-
 gcc/rust/util/rust-optional-test.cc | 3 +--
 13 files changed, 14 insertions(+), 29 deletions(-)

                 reply	other threads:[~2022-10-27 18:56 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=20221027185613.F2955384B13A@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).