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 #1739
Date: Tue, 7 Feb 2023 17:56:41 +0000 (GMT) [thread overview]
Message-ID: <20230207175641.D10903858C33@sourceware.org> (raw)
https://gcc.gnu.org/g:8f1fce4916520b7ee9a97d2bb4f25d25fd94a626
commit 8f1fce4916520b7ee9a97d2bb4f25d25fd94a626
Merge: 47a9a9e949d 6d7a7b22882
Author: bors[bot] <26634292+bors[bot]@users.noreply.github.com>
Date: Sun Feb 5 00:56:44 2023 +0000
Merge #1739
1739: Initial type bounds checking for all type checks r=philberty a=philberty
This patchset is my branch for general improvements to the type-system and
for improved type bounds checking in preparation for opaque types.
Fixes #1773 #1786
Co-authored-by: Philip Herron <herron.philip@googlemail.com>
Diff:
gcc/rust/Make-lang.in | 5 +-
gcc/rust/backend/rust-compile-expr.cc | 6 +-
gcc/rust/typecheck/rust-coercion.cc | 6 +-
gcc/rust/typecheck/rust-hir-path-probe.cc | 453 +++++
gcc/rust/typecheck/rust-hir-path-probe.h | 382 +----
...-hir-trait-ref.h => rust-hir-trait-reference.h} | 6 +-
gcc/rust/typecheck/rust-hir-trait-resolve.cc | 42 +-
gcc/rust/typecheck/rust-hir-trait-resolve.h | 9 +-
gcc/rust/typecheck/rust-hir-type-check-base.cc | 15 +-
gcc/rust/typecheck/rust-hir-type-check-path.cc | 36 +-
gcc/rust/typecheck/rust-hir-type-check.h | 334 +---
gcc/rust/typecheck/rust-substitution-mapper.cc | 343 ++++
gcc/rust/typecheck/rust-substitution-mapper.h | 286 +---
gcc/rust/typecheck/rust-tyctx.cc | 190 --
gcc/rust/typecheck/rust-typecheck-context.cc | 569 ++++++
gcc/rust/typecheck/rust-tyty-bounds.cc | 26 +-
gcc/rust/typecheck/rust-tyty-bounds.h | 88 +
gcc/rust/typecheck/rust-tyty-call.cc | 6 -
gcc/rust/typecheck/rust-tyty-rules.h | 1406 ---------------
gcc/rust/typecheck/rust-tyty-subst.cc | 1027 +++++++++++
gcc/rust/typecheck/rust-tyty-subst.h | 317 ++++
gcc/rust/typecheck/rust-tyty-util.cc | 116 ++
gcc/rust/typecheck/rust-tyty-util.h | 69 +
gcc/rust/typecheck/rust-tyty.cc | 1807 ++++++++++++--------
gcc/rust/typecheck/rust-tyty.h | 1420 +++------------
gcc/rust/typecheck/rust-unify.cc | 1651 ++++++++++++++++++
gcc/rust/typecheck/rust-unify.h | 91 +
gcc/rust/util/rust-lang-item.h | 24 +
gcc/testsuite/rust/bounds1.rs | 19 +
gcc/testsuite/rust/compile/func3.rs | 1 -
gcc/testsuite/rust/compile/issue-1773.rs | 20 +
gcc/testsuite/rust/compile/issue-1786.rs | 23 +
.../compile/{never_type_err1.rs => never_type1.rs} | 3 +-
gcc/testsuite/rust/compile/torture/intrinsics-4.rs | 63 +-
gcc/testsuite/rust/compile/torture/intrinsics-5.rs | 66 +-
gcc/testsuite/rust/execute/torture/atomic_load.rs | 59 +-
gcc/testsuite/rust/execute/torture/atomic_store.rs | 59 +-
gcc/testsuite/rust/execute/torture/issue-1720-2.rs | 30 +
38 files changed, 6625 insertions(+), 4448 deletions(-)
reply other threads:[~2023-02-07 17:56 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=20230207175641.D10903858C33@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).