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 #1409
Date: Fri, 22 Jul 2022 13:35:01 +0000 (GMT)	[thread overview]
Message-ID: <20220722133501.9199F3835436@sourceware.org> (raw)

https://gcc.gnu.org/g:15d4bdd84a7aca62bceb9dead770fd1df4759360

commit 15d4bdd84a7aca62bceb9dead770fd1df4759360
Merge: dc9981eb313 1ab1464228a
Author: bors[bot] <26634292+bors[bot]@users.noreply.github.com>
Date:   Fri Jul 22 10:34:21 2022 +0000

    Merge #1409
    
    1409: checks: Refactor project architecture for checking passes r=CohenArthur a=CohenArthur
    
    This commit adds a new `checks/` folder in the root of the Rust
    frontend, which then contains a folder for `lints` and one for `errors`
    passes. Otherwise, some error reporting passes like the privacy checks
    or upcoming unsafe visitor would have to live in their own folder in the
    root, or be part of another folder like `typecheck` or `hir` which
    doesn't necessarily makes sense. This should enable us to find them more
    easily going forward
    
    
    Co-authored-by: Arthur Cohen <arthur.cohen@embecosm.com>

Diff:

 gcc/rust/Make-lang.in                                  | 18 ++++++++++++------
 .../{ => checks/errors}/privacy/rust-privacy-check.cc  |  0
 .../{ => checks/errors}/privacy/rust-privacy-check.h   |  0
 .../{ => checks/errors}/privacy/rust-privacy-common.h  |  0
 .../{ => checks/errors}/privacy/rust-privacy-ctx.cc    |  0
 .../{ => checks/errors}/privacy/rust-privacy-ctx.h     |  0
 .../errors}/privacy/rust-privacy-reporter.cc           |  0
 .../errors}/privacy/rust-privacy-reporter.h            |  0
 .../errors}/privacy/rust-pub-restricted-visitor.cc     |  0
 .../errors}/privacy/rust-pub-restricted-visitor.h      |  0
 .../{ => checks/errors}/privacy/rust-reachability.cc   |  0
 .../{ => checks/errors}/privacy/rust-reachability.h    |  0
 .../errors}/privacy/rust-visibility-resolver.cc        |  0
 .../errors}/privacy/rust-visibility-resolver.h         |  0
 .../{lint => checks/lints}/rust-lint-marklive-base.h   |  0
 gcc/rust/{lint => checks/lints}/rust-lint-marklive.cc  |  0
 gcc/rust/{lint => checks/lints}/rust-lint-marklive.h   |  0
 .../{lint => checks/lints}/rust-lint-scan-deadcode.h   |  0
 .../{lint => checks/lints}/rust-lint-unused-var.cc     |  0
 gcc/rust/{lint => checks/lints}/rust-lint-unused-var.h |  0
 20 files changed, 12 insertions(+), 6 deletions(-)


                 reply	other threads:[~2022-07-22 13:35 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=20220722133501.9199F3835436@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).