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 #1082
Date: Wed,  8 Jun 2022 12:30:05 +0000 (GMT)	[thread overview]
Message-ID: <20220608123005.8C23D386DC7F@sourceware.org> (raw)

https://gcc.gnu.org/g:7430791e0f71f1882a0f856c496071b76c61a6bc

commit 7430791e0f71f1882a0f856c496071b76c61a6bc
Merge: 2076e69bf92 1e5126022d8
Author: bors[bot] <26634292+bors[bot]@users.noreply.github.com>
Date:   Tue Apr 12 14:32:53 2022 +0000

    Merge #1082
    
    1082: Add base for privacy visitor r=CohenArthur a=CohenArthur
    
    This PR is extremely early and implements some building blocks for privacy visitors. I'd like to get some feedback on the architecture and, if satisfactory, merge this first "visitor" which only takes care of visiting HIR struct definitions, to make reviewing easier. We could also merge it to a different branch for now, in order to not add an incomplete pass to the compiler.
    
    Thanks!
    
    Co-authored-by: Arthur Cohen <arthur.cohen@embecosm.com>

Diff:

 gcc/rust/Make-lang.in                    |   9 ++
 gcc/rust/hir/tree/rust-hir-item.h        |  11 ++-
 gcc/rust/hir/tree/rust-hir.h             |  61 ++++++++++--
 gcc/rust/privacy/rust-privacy-check.cc   |  49 ++++++++++
 gcc/rust/privacy/rust-privacy-check.h    |  45 +++++++++
 gcc/rust/privacy/rust-privacy-ctx.cc     |  93 ++++++++++++++++++
 gcc/rust/privacy/rust-privacy-ctx.h      |  79 ++++++++++++++++
 gcc/rust/privacy/rust-reachability.cc    | 157 +++++++++++++++++++++++++++++++
 gcc/rust/privacy/rust-reachability.h     |  72 ++++++++++++++
 gcc/rust/rust-lang.cc                    |   3 +
 gcc/rust/rust-session-manager.cc         |   4 +
 gcc/rust/typecheck/rust-hir-type-check.h |   2 +-
 gcc/rust/typecheck/rust-tyctx.cc         |   2 +-
 gcc/rust/util/rust-mapping-common.h      |  13 +++
 14 files changed, 591 insertions(+), 9 deletions(-)


                 reply	other threads:[~2022-06-08 12:30 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=20220608123005.8C23D386DC7F@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).