From: Jakub Jelinek <jakub@redhat.com>
To: Jason Merrill <jason@redhat.com>
Cc: gcc-patches@gcc.gnu.org
Subject: [C++ PATCH] Pass RUNTESTFLAGS through from check-c++1z
Date: Fri, 23 Sep 2016 17:25:00 -0000 [thread overview]
Message-ID: <20160923172301.GV7282@tucnak.redhat.com> (raw)
Hi!
I've been surprised that
make check-c++1z RUNTESTFLAGS=dg.exp=direct-enum*
attempts to run the whole testsuite in -std=c++1z mode,
while if I replace check-c++1z with check-g++ or check-c++-all,
it works properly.
The following patch passes the var down to the submake, so that it works
as expected. Ok for trunk?
2016-09-23 Jakub Jelinek <jakub@redhat.com>
* Make-lang.in (check-c++1z): Pass RUNTESTFLAGS down to
make check-g++.
--- gcc/cp/Make-lang.in.jj 2016-06-28 14:13:37.000000000 +0200
+++ gcc/cp/Make-lang.in 2016-09-23 19:16:54.382005180 +0200
@@ -164,7 +164,7 @@ check-c++ : check-g++
# Run the testsuite in C++1z mode.
check-c++1z:
- $(MAKE) GXX_TESTSUITE_STDS=1z check-g++
+ $(MAKE) RUNTESTFLAGS="$(RUNTESTFLAGS)" GXX_TESTSUITE_STDS=1z check-g++
# Run the testsuite in all standard conformance levels.
check-c++-all:
Jakub
next reply other threads:[~2016-09-23 17:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-23 17:25 Jakub Jelinek [this message]
2016-09-23 17:37 ` Jason Merrill
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=20160923172301.GV7282@tucnak.redhat.com \
--to=jakub@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.com \
/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).