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 #1265
Date: Wed,  8 Jun 2022 12:48:53 +0000 (GMT)	[thread overview]
Message-ID: <20220608124853.5139E3810AF9@sourceware.org> (raw)

https://gcc.gnu.org/g:55ec3454d0d45829431d8904aa0b6363ac362616

commit 55ec3454d0d45829431d8904aa0b6363ac362616
Merge: 93e59035536 39ae84825c5
Author: bors[bot] <26634292+bors[bot]@users.noreply.github.com>
Date:   Mon May 23 08:58:04 2022 +0000

    Merge #1265
    
    1265: Canonicalize types based on hashing than HirIds and TyTy equality r=philberty a=philberty
    
    This patch updates how we canonicalize the types. The old method was not
    able to handle more complex cases involving generic associated types. So
    this now uses a moe generic hashing system which now speeds up the lookups.
    
    The commit message gives much more detail here.
    
    Co-authored-by: Philip Herron <philip.herron@embecosm.com>

Diff:

 gcc/rust/Make-lang.in                             |   1 +
 gcc/rust/backend/rust-compile-block.h             |   1 -
 gcc/rust/backend/rust-compile-context.cc          | 139 ++++++++++++
 gcc/rust/backend/rust-compile-context.h           |  71 ++----
 gcc/rust/backend/rust-compile-expr.h              |   1 -
 gcc/rust/backend/rust-compile-resolve-path.h      |   1 -
 gcc/rust/backend/rust-compile-stmt.h              |   1 -
 gcc/rust/backend/rust-compile-struct-field-expr.h |   1 -
 gcc/rust/backend/rust-compile-type.cc             | 202 ++++++++++-------
 gcc/rust/backend/rust-compile-type.h              |  12 +-
 gcc/rust/backend/rust-compile-tyty.h              | 260 ----------------------
 gcc/rust/backend/rust-mangle.h                    |   3 +-
 12 files changed, 291 insertions(+), 402 deletions(-)


                 reply	other threads:[~2022-06-08 12:48 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=20220608124853.5139E3810AF9@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).