From: Iain Sandoe <iain@sandoe.co.uk>
To: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: [PATCH] configure, jit: Allow for 'make check-gcc-jit'.
Date: Tue, 17 Aug 2021 19:59:39 +0100 [thread overview]
Message-ID: <3F9EABCC-7A0C-4B86-BEE8-78BB4303D3EF@sandoe.co.uk> (raw)
Hi,
For those of us who habitually build Ada, it’s convenient to
have a way of running individual test suites without invoking
the acats tests…
being able to do “make check-gcc-jit” from the top level is very
useful when debugging jit testsuite issues.
one can do "cd gcc ; make check-jit "- but this doesn’t seem 100%
identical since the invocations from the top level set the host
exports first.
… the patch itself is trivial / obvious - I am just curious as to
whether there was a reason for omitting it so far?
If not,
OK for master?
thanks
Iain
====
This is a convenience feature that allows the user to
do "make check-gcc-jit" at the top level of the build
to check that facility in isolation from others.
Signed-off-by: Iain Sandoe <iain@sandoe.co.uk>
ChangeLog:
* Makefile.def: Add a jit check target for the jit
language.
* Makefile.in: Regenerate.
---
Makefile.def | 1 +
Makefile.in | 8 ++++++++
2 files changed, 9 insertions(+)
diff --git a/Makefile.def b/Makefile.def
index fbfdb6fee08..7cbeca5b181 100644
--- a/Makefile.def
+++ b/Makefile.def
@@ -654,6 +654,7 @@ languages = { language=go; gcc-check-target=check-go;
lib-check-target=check-gotools; };
languages = { language=d; gcc-check-target=check-d;
lib-check-target=check-target-libphobos; };
+languages = { language=jit; gcc-check-target=check-jit; };
// Toplevel bootstrap
bootstrap_stage = { id=1 ; };
next reply other threads:[~2021-08-17 18:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-17 18:59 Iain Sandoe [this message]
2021-08-17 20:53 ` David Malcolm
2021-08-27 13:00 ` [PING] " Iain Sandoe
2021-09-15 19:28 ` [PING^2] " Iain Sandoe
2021-09-17 3:09 ` Jeff Law
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=3F9EABCC-7A0C-4B86-BEE8-78BB4303D3EF@sandoe.co.uk \
--to=iain@sandoe.co.uk \
--cc=gcc-patches@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).