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 r13-6272] Rust: Move void_list_node init to common code
Date: Wed, 22 Feb 2023 09:18:28 +0000 (GMT)	[thread overview]
Message-ID: <20230222091828.C86743858D33@sourceware.org> (raw)

https://gcc.gnu.org/g:334f23d83261997ca89d8919b94b97aa22003a65

commit r13-6272-g334f23d83261997ca89d8919b94b97aa22003a65
Author: Thomas Schwinge <thomas@codesourcery.com>
Date:   Wed Feb 22 10:15:19 2023 +0100

    Rust: Move void_list_node init to common code
    
    Apply commit r13-2682-g8ff2a92a0450243e52d3299a13b30f208bafa7e0
    "Move void_list_node init to common code" to the Rust front end, too.
    
            gcc/rust/
            * rust-lang.cc (grs_langhook_init): Do not initialize
            void_list_node.

Diff:
---
 gcc/rust/rust-lang.cc | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/gcc/rust/rust-lang.cc b/gcc/rust/rust-lang.cc
index 75f6b4458d7..3e20c45d907 100644
--- a/gcc/rust/rust-lang.cc
+++ b/gcc/rust/rust-lang.cc
@@ -123,10 +123,6 @@ grs_langhook_init (void)
    whether char is signed.  */
   build_common_tree_nodes (false);
 
-  // Creates a new TREE_LIST node with purpose NULL_TREE and value
-  // void_type_node
-  void_list_node = build_tree_list (NULL_TREE, void_type_node);
-
   // Builds built-ins for middle-end after all front-end built-ins are already
   // instantiated
   build_common_builtin_nodes ();

                 reply	other threads:[~2023-02-22  9:18 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=20230222091828.C86743858D33@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).