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 #1431
Date: Sat,  6 Aug 2022 12:10:26 +0000 (GMT)	[thread overview]
Message-ID: <20220806121026.2C610385841D@sourceware.org> (raw)

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

commit a39108dea1d091545982fefa88ce3be31b9eedf2
Merge: e77bc10ba13 5d17a8b6b2c
Author: bors[bot] <26634292+bors[bot]@users.noreply.github.com>
Date:   Fri Aug 5 10:09:20 2022 +0000

    Merge #1431
    
    1431: Incremental refactor for better coercion site support r=philberty a=philberty
    
    This is the major refactor to get our coercion site code closer to Rustc.
    It introduced several new pieces most notably a refactor to the autoderef
    cycle so this can be reused in method resolution and in coercion sites which
    allows us to handle deref coercions. It will eventually allow us to get rid
    of our bad implementation in rust-tyty-coercion.h which is just messy now.
    
    Fixes #1198
    
    Co-authored-by: Philip Herron <philip.herron@embecosm.com>

Diff:

 gcc/rust/Make-lang.in                            |   2 +
 gcc/rust/backend/rust-compile-base.cc            |  14 +-
 gcc/rust/backend/rust-compile-base.h             |   9 +-
 gcc/rust/backend/rust-compile-expr.cc            | 103 +++------
 gcc/rust/backend/rust-compile-expr.h             |  28 +--
 gcc/rust/backend/rust-compile-extern.h           |   9 +-
 gcc/rust/backend/rust-compile-implitem.cc        |  10 +-
 gcc/rust/backend/rust-compile-item.cc            |   9 +-
 gcc/rust/backend/rust-compile-resolve-path.cc    |   6 +-
 gcc/rust/backend/rust-compile-stmt.h             |   3 +-
 gcc/rust/backend/rust-compile.cc                 |  55 ++---
 gcc/rust/hir/tree/rust-hir-expr.h                |  26 ++-
 gcc/rust/rust-backend.h                          |   8 -
 gcc/rust/rust-gcc.cc                             |  24 --
 gcc/rust/typecheck/rust-autoderef.cc             | 124 +++++++++++
 gcc/rust/typecheck/rust-autoderef.h              |  21 ++
 gcc/rust/typecheck/rust-coercion.cc              |  92 ++++++++
 gcc/rust/typecheck/rust-coercion.h               |  70 ++++++
 gcc/rust/typecheck/rust-hir-dot-operator.cc      | 177 +++------------
 gcc/rust/typecheck/rust-hir-dot-operator.h       |  41 ++--
 gcc/rust/typecheck/rust-hir-type-check-base.cc   |  22 ++
 gcc/rust/typecheck/rust-hir-type-check-base.h    |   3 +
 gcc/rust/typecheck/rust-hir-type-check-expr.cc   | 157 ++++++++++++-
 gcc/rust/typecheck/rust-hir-type-check-expr.h    | 155 +------------
 gcc/rust/typecheck/rust-hir-type-check-stmt.h    |   3 +-
 gcc/rust/typecheck/rust-hir-type-check-struct.cc |  16 +-
 gcc/rust/typecheck/rust-tyty-call.cc             | 269 +++++++++++++++++++++++
 gcc/rust/typecheck/rust-tyty-cmp.h               | 106 ++++++++-
 gcc/rust/typecheck/rust-tyty.cc                  | 238 --------------------
 gcc/testsuite/rust/compile/generics4.rs          |   7 +-
 gcc/testsuite/rust/compile/reference1.rs         |   3 +-
 gcc/testsuite/rust/compile/shadow1.rs            |   3 +-
 gcc/testsuite/rust/compile/type-bindings1.rs     |   1 -
 gcc/testsuite/rust/execute/torture/issue-1198.rs |  75 +++++++
 34 files changed, 1122 insertions(+), 767 deletions(-)


                 reply	other threads:[~2022-08-06 12:10 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=20220806121026.2C610385841D@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).