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 #1339 Date: Tue, 28 Jun 2022 12:39:23 +0000 (GMT) [thread overview] Message-ID: <20220628123923.2CBC63885A1E@sourceware.org> (raw) https://gcc.gnu.org/g:80a14bd8138553596fd8cf93fcafcb1429d8b30e commit 80a14bd8138553596fd8cf93fcafcb1429d8b30e Merge: 5bab921fc01 40ad6b290af Author: bors[bot] <26634292+bors[bot]@users.noreply.github.com> Date: Mon Jun 27 08:07:14 2022 +0000 Merge #1339 1339: Add `line!` macro r=CohenArthur a=graphman65 Co-authored-by: Sebastien Lacoste <dev@graphman.fr> Diff: gcc/rust/expand/rust-macro-builtins.cc | 16 ++++++++++++++-- gcc/rust/expand/rust-macro-builtins.h | 3 +++ gcc/rust/util/rust-hir-map.cc | 1 + .../rust/execute/torture/builtin_macro_line.rs | 22 ++++++++++++++++++++++ 4 files changed, 40 insertions(+), 2 deletions(-)
reply other threads:[~2022-06-28 12:39 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=20220628123923.2CBC63885A1E@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).