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 #1583
Date: Fri, 14 Oct 2022 12:46:03 +0000 (GMT)	[thread overview]
Message-ID: <20221014124603.89BCA3857BAD@sourceware.org> (raw)

https://gcc.gnu.org/g:84ca2f9123a7d5206d70d5b3bdc18d98c0cee2e0

commit 84ca2f9123a7d5206d70d5b3bdc18d98c0cee2e0
Merge: 8cbcff46d34 32e45c4076c
Author: bors[bot] <26634292+bors[bot]@users.noreply.github.com>
Date:   Fri Oct 14 08:52:42 2022 +0000

    Merge #1583
    
    1583: Support type resolution on super traits on dyn objects r=philberty a=philberty
    
    When checking if specified bounds satisfy other bounds we must lookup the super traits. To finish the support for super traits we need to redo the computation of method addresses to support super traits.
    
    Addresses #914
    
    
    Co-authored-by: Philip Herron <philip.herron@embecosm.com>

Diff:

 gcc/rust/backend/rust-compile.cc        |  2 ++
 gcc/rust/typecheck/rust-hir-trait-ref.h | 24 ++++++++++++++++++++++
 gcc/rust/typecheck/rust-tyty.cc         | 35 +++++++++++----------------------
 3 files changed, 37 insertions(+), 24 deletions(-)

                 reply	other threads:[~2022-10-14 12:46 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=20221014124603.89BCA3857BAD@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).