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 #1532
Date: Mon, 26 Sep 2022 11:04:36 +0000 (GMT)	[thread overview]
Message-ID: <20220926110436.53E0E3858CDA@sourceware.org> (raw)

https://gcc.gnu.org/g:cfd2938f069598e9be25484f16ac045606c69e72

commit cfd2938f069598e9be25484f16ac045606c69e72
Merge: 6da3cab7b0a c71b174a29c
Author: bors[bot] <26634292+bors[bot]@users.noreply.github.com>
Date:   Mon Sep 26 06:58:57 2022 +0000

    Merge #1532
    
    1532: attributes: Add #[macro_use] as builtin r=CohenArthur a=CohenArthur
    
    Fixes #1531
    
    I think the checking for builtin attributes should definitely be moved to the `AttributeChecker` visitor. It's also a bit messy at the moment considering it isn't in effect on *everything*, simply some nodes such as `Module`s. Thoughts?
    
    Co-authored-by: Arthur Cohen <arthur.cohen@embecosm.com>

Diff:

 gcc/rust/util/rust-attributes.cc             | 1 +
 gcc/testsuite/rust/compile/macro_export_1.rs | 2 ++
 2 files changed, 3 insertions(+)

                 reply	other threads:[~2022-09-26 11:04 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=20220926110436.53E0E3858CDA@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).