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 #1283
Date: Wed,  8 Jun 2022 12:50:50 +0000 (GMT)	[thread overview]
Message-ID: <20220608125050.29174388B59D@sourceware.org> (raw)

https://gcc.gnu.org/g:7a94948e65db2fef6fd93c94e70ead168b71513d

commit 7a94948e65db2fef6fd93c94e70ead168b71513d
Merge: a4455d8f522 1a04c501e41
Author: bors[bot] <26634292+bors[bot]@users.noreply.github.com>
Date:   Thu May 26 18:50:14 2022 +0000

    Merge #1283
    
    1283: const folding in gccrs: remove ConstCtx class. r=philberty a=abbasfaisal
    
    Card: [Link](https://github.com/Rust-GCC/gccrs/projects/16#card-82300522)
    
    This class had potential to hinder porting further const folding code from C++. This edit makes it easy to copy code from constexpr.cc to rust-constexpr.cc and so on.
    
    Structs `constexpr_ctx` and `constexpr_global_ctx` have been copied as well as to keep `constexpr_ops_count` after removing the class. These structs will be filled further as the port carries on. The prototypes inside ConstCtx have been copied over to rust-constexpr.cc as static prototypes.
    
    
    Co-authored-by: Faisal Abbas <90.abbasfaisal@gmail.com>

Diff:

 gcc/rust/backend/rust-compile-base.cc         |  4 +-
 gcc/rust/backend/rust-compile-expr.cc         |  2 +-
 gcc/rust/backend/rust-compile-expr.h          |  2 +-
 gcc/rust/backend/rust-compile-pattern.cc      |  6 +-
 gcc/rust/backend/rust-compile-resolve-path.cc |  2 +-
 gcc/rust/backend/rust-compile-type.cc         |  2 +-
 gcc/rust/backend/rust-constexpr.cc            | 86 ++++++++++++++++++---------
 gcc/rust/backend/rust-constexpr.h             | 17 +-----
 8 files changed, 67 insertions(+), 54 deletions(-)


                 reply	other threads:[~2022-06-08 12:50 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=20220608125050.29174388B59D@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).