public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Arthur Cohen <cohenarthur@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r13-4637] gccrs: Add gcc-check-target check-rust
Date: Tue, 13 Dec 2022 13:17:21 +0000 (GMT)	[thread overview]
Message-ID: <20221213131721.7018138432F5@sourceware.org> (raw)

https://gcc.gnu.org/g:dc4171edb3c35690c67a928cbb431aa702bdbe79

commit r13-4637-gdc4171edb3c35690c67a928cbb431aa702bdbe79
Author: Philip Herron <philip.herron@embecosm.com>
Date:   Tue Aug 23 16:04:30 2022 +0100

    gccrs: Add gcc-check-target check-rust
    
    This allows us to invoke the rust testsuite.
    
            * Makefile.def: Add Rust language.
            * Makefile.in: Regenerate via autogen.

Diff:
---
 Makefile.def | 1 +
 Makefile.in  | 8 ++++++++
 2 files changed, 9 insertions(+)

diff --git a/Makefile.def b/Makefile.def
index 25e48938dbf..c67eb567783 100644
--- a/Makefile.def
+++ b/Makefile.def
@@ -676,6 +676,7 @@ languages = { language=go;	gcc-check-target=check-go;
 languages = { language=d;	gcc-check-target=check-d;
 				lib-check-target=check-target-libphobos; };
 languages = { language=jit;	gcc-check-target=check-jit; };
+languages = { language=rust;	gcc-check-target=check-rust; };
 
 // Toplevel bootstrap
 bootstrap_stage = { id=1 ; };
diff --git a/Makefile.in b/Makefile.in
index c426b0607c4..fad49011e61 100644
--- a/Makefile.in
+++ b/Makefile.in
@@ -61237,6 +61237,14 @@ check-gcc-jit:
 	(cd gcc && $(MAKE) $(GCC_FLAGS_TO_PASS) check-jit);
 check-jit: check-gcc-jit
 
+.PHONY: check-gcc-rust check-rust
+check-gcc-rust:
+	r=`${PWD_COMMAND}`; export r; \
+	s=`cd $(srcdir); ${PWD_COMMAND}`; export s; \
+	$(HOST_EXPORTS) \
+	(cd gcc && $(MAKE) $(GCC_FLAGS_TO_PASS) check-rust);
+check-rust: check-gcc-rust
+
 
 # The gcc part of install-no-fixedincludes, which relies on an intimate
 # knowledge of how a number of gcc internal targets (inter)operate.  Delegate.

                 reply	other threads:[~2022-12-13 13:17 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=20221213131721.7018138432F5@sourceware.org \
    --to=cohenarthur@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).