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 #1151 #1343
Date: Thu, 30 Jun 2022 18:50:58 +0000 (GMT)	[thread overview]
Message-ID: <20220630185058.2AABA383F978@sourceware.org> (raw)

https://gcc.gnu.org/g:81abc8623cb75fa18315c65e94c5965ec36fdb54

commit 81abc8623cb75fa18315c65e94c5965ec36fdb54
Merge: 9976c571ff1 0c290e7c6f3 1282974cf89
Author: bors[bot] <26634292+bors[bot]@users.noreply.github.com>
Date:   Wed Jun 29 14:07:33 2022 +0000

    Merge #1151 #1343
    
    1151: backend: handle deprecated attribute r=philberty a=liushuyu
    
    - handle the `deprecated` attribute
    
    1343: Ensure we support generic arguments on mangled type-paths r=philberty a=philberty
    
    This allows us to have the generic arguments within type paths for mangled
    symbols such as those in impl-blocks. This also updates our symbol
    managling to mangle comma's to $C$.
    
    
    Co-authored-by: liushuyu <liushuyu011@gmail.com>
    Co-authored-by: Philip Herron <philip.herron@embecosm.com>

Diff:

 gcc/rust/ast/rust-ast-full-test.cc              |  9 ++-
 gcc/rust/ast/rust-ast.h                         |  2 +
 gcc/rust/ast/rust-macro.h                       |  8 +++
 gcc/rust/backend/rust-compile-base.cc           | 73 ++++++++++++++++++++++++-
 gcc/rust/backend/rust-compile-base.h            |  3 +
 gcc/rust/backend/rust-mangle.cc                 |  6 ++
 gcc/rust/resolve/rust-ast-resolve-type.cc       | 47 +++++++++++++++-
 gcc/rust/rust-gcc.cc                            | 10 ++++
 gcc/rust/util/rust-attributes.cc                |  1 +
 gcc/testsuite/rust/compile/attr_deprecated.rs   | 14 +++++
 gcc/testsuite/rust/compile/attr_deprecated_2.rs | 11 ++++
 11 files changed, 181 insertions(+), 3 deletions(-)


                 reply	other threads:[~2022-06-30 18:50 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=20220630185058.2AABA383F978@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).