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 #1425 #1451
Date: Tue,  9 Aug 2022 20:39:40 +0000 (GMT)	[thread overview]
Message-ID: <20220809203940.8246D3858038@sourceware.org> (raw)

https://gcc.gnu.org/g:5865fb27a73a6e7483bc98ba5f33c7f8bc850790

commit 5865fb27a73a6e7483bc98ba5f33c7f8bc850790
Merge: 17b625cbd61 0ec8f938272 92eef6c33d4
Author: bors[bot] <26634292+bors[bot]@users.noreply.github.com>
Date:   Tue Aug 9 14:25:07 2022 +0000

    Merge #1425 #1451
    
    1425: Cleanup frontend entrypoint r=CohenArthur a=CohenArthur
    
    This removes a lot of code that was simply ported from the Go frontend, and forbids the usage of multiple input files.
    
    Addresses #1115
    
    1451: Fix failiure to type inference on unit-structs r=philberty a=philberty
    
    This patch set adds fixes to ensure we can type inference generic unit-structs.
    
    Fixes #1447
    
    Co-authored-by: Arthur Cohen <arthur.cohen@embecosm.com>
    Co-authored-by: Philip Herron <philip.herron@embecosm.com>

Diff:

 gcc/rust/rust-lang.cc                         |  36 +------
 gcc/rust/rust-session-manager.cc              |  23 +++--
 gcc/rust/rust-session-manager.h               |   4 +-
 gcc/rust/rustspec.cc                          | 131 +++-----------------------
 gcc/rust/typecheck/rust-hir-type-check-expr.h |  11 +++
 gcc/rust/typecheck/rust-tyty-coercion.h       |  46 +++++++++
 gcc/rust/typecheck/rust-tyty-rules.h          |  34 +++++++
 gcc/testsuite/rust/compile/issue-1447.rs      |  28 ++++++
 8 files changed, 145 insertions(+), 168 deletions(-)


                 reply	other threads:[~2022-08-09 20:39 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=20220809203940.8246D3858038@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).