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 #1607
Date: Sat, 22 Oct 2022 10:48:42 +0000 (GMT)	[thread overview]
Message-ID: <20221022104842.0421E3858C62@sourceware.org> (raw)

https://gcc.gnu.org/g:60b21d2f58f46c93fc33f6192682abfed62d8dd9

commit 60b21d2f58f46c93fc33f6192682abfed62d8dd9
Merge: dfb5921b765 89490980726
Author: bors[bot] <26634292+bors[bot]@users.noreply.github.com>
Date:   Fri Oct 21 13:05:18 2022 +0000

    Merge #1607
    
    1607: Improve AST Fragment class r=CohenArthur a=CohenArthur
    
    This changes the APIs around creating AST fragments and refactors the class into its own header and source file, hopefully making it easier to use. This will also help creating "unexpanded" AST fragments for proper builtin macro expansion with the new fixed-point algorithm introduced by #1606
    
    `@liushuyu` pinging you since you've worked extensively with the macro system. Would love your review!
    
    Co-authored-by: Arthur Cohen <arthur.cohen@embecosm.com>

Diff:

 gcc/rust/Make-lang.in                    |   1 +
 gcc/rust/ast/rust-ast-fragment.cc        | 171 +++++++++++++++++++++++++++++++
 gcc/rust/ast/rust-ast-fragment.h         | 118 +++++++++++++++++++++
 gcc/rust/ast/rust-ast.h                  | 132 ------------------------
 gcc/rust/ast/rust-macro.h                |  18 ++--
 gcc/rust/expand/rust-attribute-visitor.h |   4 +-
 gcc/rust/expand/rust-macro-builtins.cc   |  72 ++++++-------
 gcc/rust/expand/rust-macro-builtins.h    |  40 ++++----
 gcc/rust/expand/rust-macro-expand.cc     |  42 ++++----
 gcc/rust/expand/rust-macro-expand.h      |  23 ++---
 gcc/rust/util/rust-hir-map.cc            |   4 +-
 11 files changed, 390 insertions(+), 235 deletions(-)

                 reply	other threads:[~2022-10-22 10:48 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=20221022104842.0421E3858C62@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).