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 #1708 Date: Thu, 12 Jan 2023 07:44:44 +0000 (GMT) [thread overview] Message-ID: <20230112074444.B8BDA385438F@sourceware.org> (raw) https://gcc.gnu.org/g:3290293e16fa47cf59f0434343c1bf40497ede90 commit 3290293e16fa47cf59f0434343c1bf40497ede90 Merge: 48d32bc9cb0 9e5769cf45c Author: bors[bot] <26634292+bors[bot]@users.noreply.github.com> Date: Mon Jan 9 15:48:12 2023 +0000 Merge #1708 1708: Parse declarative macro (decl_macro 2.0) r=CohenArthur a=tamaroning This PR is currentry wip. Opinions and advices are welcome! Co-authored-by: Raiki Tamura <tamaron1203@gmail.com> Diff: gcc/rust/ast/rust-ast-full-decls.h | 1 - gcc/rust/ast/rust-ast-full-test.cc | 1 + gcc/rust/ast/rust-ast.h | 5 - gcc/rust/ast/rust-item.h | 2 - gcc/rust/ast/rust-macro.h | 65 ++++-- gcc/rust/lex/rust-token.h | 2 +- gcc/rust/parse/rust-parse-impl.h | 229 +++++++++++++++++----- gcc/rust/parse/rust-parse.h | 3 +- gcc/testsuite/rust/compile/decl_macro1.rs | 2 + gcc/testsuite/rust/compile/decl_macro2.rs | 2 + gcc/testsuite/rust/compile/decl_macro3.rs | 4 + gcc/testsuite/rust/compile/decl_macro4.rs | 5 + gcc/testsuite/rust/compile/decl_macro5.rs | 5 + gcc/testsuite/rust/compile/decl_macro6.rs | 5 + gcc/testsuite/rust/compile/decl_macro7.rs | 4 + gcc/testsuite/rust/execute/torture/decl_macro1.rs | 8 + gcc/testsuite/rust/execute/torture/decl_macro2.rs | 8 + gcc/testsuite/rust/execute/torture/decl_macro3.rs | 15 ++ gcc/testsuite/rust/execute/torture/decl_macro4.rs | 15 ++ 19 files changed, 301 insertions(+), 80 deletions(-)
reply other threads:[~2023-01-12 7:44 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=20230112074444.B8BDA385438F@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: linkBe 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).