From: Tom Tromey <tromey@adacore.com>
To: Tom de Vries <tdevries@suse.de>
Cc: Tom Tromey <tromey@adacore.com>,
Simon Marchi <simon.marchi@polymtl.ca>,
gdb-patches@sourceware.org
Subject: Re: [PATCH 1/5] Remove gdb/testsuite/configure
Date: Wed, 09 Jun 2021 08:35:49 -0600 [thread overview]
Message-ID: <87lf7jjebe.fsf@tromey.com> (raw)
In-Reply-To: <aa3aa4de-461f-0be5-f68e-86876a7332ce@suse.de> (Tom de Vries's message of "Sat, 5 Jun 2021 11:51:05 +0200")
>> Sure. If anybody relies on being able to do this without using 'make',
>> there's already a 'read1' convenience target that can be used.
>>
>> I'm going to check this in with this change.
Tom> Personally I'm fine with no longer supporting this. But perhaps others
Tom> use READ1=1 in combination with some nonstandard make target? I'm not sure.
There's no way to know.
We can restore the old behavior if you think that's worthwhile.
Tom> Anyway, if we decide to leave things as they are now, we should document
Tom> this in gdb/testsuite/README:
Tom> ...
Tom> Examples:
Tom> make -j10 check-read1 TESTS="*/paginate-*.exp"
Tom> - make -j10 check READ1="1"
Tom> ...
How about the appended?
Tom
commit 6bd42c74ef9b1838c9a0151fb089188de4b80e5f
Author: Tom Tromey <tromey@adacore.com>
Date: Wed Jun 9 08:34:47 2021 -0600
Update read1 example in gdb/testsuite/README
Tom de Vries noticed that the recent changes to the testsuite's
configury required an update to the README. This patch changes the
text to document the new reality.
gdb/testsuite/ChangeLog
2021-06-09 Tom Tromey <tromey@adacore.com>
* README (Example): Update read1 example.
diff --git a/gdb/testsuite/ChangeLog b/gdb/testsuite/ChangeLog
index 92894d6efab..bd06a4433fd 100644
--- a/gdb/testsuite/ChangeLog
+++ b/gdb/testsuite/ChangeLog
@@ -1,3 +1,7 @@
+2021-06-09 Tom Tromey <tromey@adacore.com>
+
+ * README (Example): Update read1 example.
+
2021-06-08 Lancelot Six <lsix@lancelotsix.com>
* gdb.base/premature-dummy-frame-removal.py (TestUnwinder): Use
diff --git a/gdb/testsuite/README b/gdb/testsuite/README
index 0036753eff0..862f423a988 100644
--- a/gdb/testsuite/README
+++ b/gdb/testsuite/README
@@ -347,9 +347,13 @@ return at most 1 byte.
To enable this, either pass a non-empty value in the READ1 make
variable, or use the check-read1 make target instead of check.
-Examples:
+Example:
make -j10 check-read1 TESTS="*/paginate-*.exp"
+
+If you've already built the read1 support code, either via a previous
+'check-read1' run, or by using "make read1", you can use:
+
make -j10 check READ1="1"
Note: While the intention is to detect races and make otherwise passing tests
next prev parent reply other threads:[~2021-06-09 14:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-28 19:27 [PATCH 0/5] Some gdb build cleanups Tom Tromey
2021-05-28 19:27 ` [PATCH 1/5] Remove gdb/testsuite/configure Tom Tromey
2021-05-29 3:44 ` Simon Marchi
2021-06-01 13:59 ` Tom Tromey
2021-06-05 9:51 ` Tom de Vries
2021-06-09 14:35 ` Tom Tromey [this message]
2021-06-09 14:46 ` Tom de Vries
2021-08-07 1:03 ` Tom de Vries
2021-05-28 19:27 ` [PATCH 2/5] Always build 'all' in gdb/testsuite Tom Tromey
2021-05-28 19:27 ` [PATCH 3/5] Apply silent Makefile rules to gdb/testsuite Tom Tromey
2021-05-28 19:27 ` [PATCH 4/5] Clean up gdb's --enable-shared Tom Tromey
2021-05-28 19:27 ` [PATCH 5/5] Remove some gdb/data-directory special cases Tom Tromey
2021-05-29 3:50 ` [PATCH 0/5] Some gdb build cleanups Simon Marchi
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=87lf7jjebe.fsf@tromey.com \
--to=tromey@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@polymtl.ca \
--cc=tdevries@suse.de \
/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).