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 #1417 Date: Thu, 28 Jul 2022 07:53:24 +0000 (GMT) [thread overview] Message-ID: <20220728075324.821463857B98@sourceware.org> (raw) https://gcc.gnu.org/g:205096066a50f501eb1c1d1f7acb4b0daa8be15a commit 205096066a50f501eb1c1d1f7acb4b0daa8be15a Merge: 50ca4b2ba00 f4e4c2444fc Author: bors[bot] <26634292+bors[bot]@users.noreply.github.com> Date: Wed Jul 27 20:19:02 2022 +0000 Merge #1417 1417: unsafe: check uses of static variables r=CohenArthur a=CohenArthur Addresses #1411 Accessing an extern static or a mut static is unsafe and requires an unsafe function or block Co-authored-by: Arthur Cohen <arthur.cohen@embecosm.com> Diff: gcc/rust/checks/errors/rust-unsafe-checker.cc | 78 +++++++++++++++++++++++++-- gcc/rust/checks/errors/rust-unsafe-checker.h | 9 ++++ gcc/rust/hir/tree/rust-hir-item.h | 37 +++++++++++++ gcc/rust/hir/tree/rust-hir.h | 20 +++++++ gcc/testsuite/rust/compile/unsafe1.rs | 14 +++++ gcc/testsuite/rust/compile/unsafe2.rs | 16 ++++++ gcc/testsuite/rust/compile/unsafe3.rs | 10 ++++ 7 files changed, 180 insertions(+), 4 deletions(-)
reply other threads:[~2022-07-28 7:53 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=20220728075324.821463857B98@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).