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] gccrs: cleanup headers
Date: Sun,  5 Mar 2023 11:42:40 +0000 (GMT)	[thread overview]
Message-ID: <20230305114240.7C9683858C36@sourceware.org> (raw)

https://gcc.gnu.org/g:99b3cfe5cdd97dc36b5807ab635e484a7d0c9aa7

commit 99b3cfe5cdd97dc36b5807ab635e484a7d0c9aa7
Author: Philip Herron <herron.philip@googlemail.com>
Date:   Fri Mar 3 16:44:43 2023 +0000

    gccrs: cleanup headers
    
    Signed-off-by: Philip Herron <herron.philip@googlemail.com>
    
    gcc/rust/ChangeLog:
    
            * rust-gcc.h: remove unused headers

Diff:
---
 gcc/rust/rust-gcc.h | 6 ------
 1 file changed, 6 deletions(-)

diff --git a/gcc/rust/rust-gcc.h b/gcc/rust/rust-gcc.h
index 0db81949270..e0aa540a1fa 100644
--- a/gcc/rust/rust-gcc.h
+++ b/gcc/rust/rust-gcc.h
@@ -19,17 +19,11 @@
 // along with GCC; see the file COPYING3.  If not see
 // <http://www.gnu.org/licenses/>.
 
-#include "rust-system.h"
-
 // This has to be included outside of extern "C", so we have to
 // include it here before tree.h includes it later.
-#include <gmp.h>
 
-#include "tree.h"
 #include "rust-location.h"
 
-// TODO: this will have to be significantly modified to work with Rust
-
 // Bvariable is a bit more complicated, because of zero-sized types.
 // The GNU linker does not permit dynamic variables with zero size.
 // When we see such a variable, we generate a version of the type with

                 reply	other threads:[~2023-03-05 11:42 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=20230305114240.7C9683858C36@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).