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 #1541
Date: Fri, 23 Sep 2022 06:52:00 +0000 (GMT)	[thread overview]
Message-ID: <20220923065200.428DA3857815@sourceware.org> (raw)

https://gcc.gnu.org/g:6da3cab7b0acf5dc363c85069bef716923ddf90c

commit 6da3cab7b0acf5dc363c85069bef716923ddf90c
Merge: f252b409366 5f01d6c5373
Author: bors[bot] <26634292+bors[bot]@users.noreply.github.com>
Date:   Thu Sep 22 12:20:49 2022 +0000

    Merge #1541
    
    1541: Static const eval safety r=philberty a=philberty
    
    This adds a test case for the rust issue: https://blog.rust-lang.org/2022/09/15/const-eval-safety-rule-revision.html
    
    Co-authored-by: Philip Herron <philip.herron@embecosm.com>

Diff:

 gcc/rust/backend/rust-compile-item.cc               |  7 ++++++-
 gcc/rust/backend/rust-tree.cc                       |  7 ++++---
 gcc/rust/typecheck/rust-hir-type-check-toplevel.cc  | 10 +++++-----
 gcc/testsuite/rust/compile/rust-const-blog-issue.rs | 12 ++++++++++++
 4 files changed, 27 insertions(+), 9 deletions(-)

                 reply	other threads:[~2022-09-23  6:52 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=20220923065200.428DA3857815@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).