This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] [docs] Explain how to use multiple file-name patterns in RUNTESTFLAGS
- From: Daniel Santos <daniel dot santos at pobox dot com>
- To: Martin Sebor <msebor at gmail dot com>, gcc-patches <gcc-patches at gcc dot gnu dot org>, Sandra Loosemore <sandra at codesourcery dot com>, Gerald Pfeifer <gerald at pfeifer dot com>, Joseph Myers <joseph at codesourcery dot com>, Rainer Orth <ro at CeBiTec dot Uni-Bielefeld dot DE>, Mike Stump <mikestump at comcast dot net>
- Date: Tue, 22 Aug 2017 12:32:44 -0500
- Subject: Re: [PATCH] [docs] Explain how to use multiple file-name patterns in RUNTESTFLAGS
- Authentication-results: sourceware.org; auth=none
- References: <20170822014151.5431-1-daniel.santos@pobox.com> <5fcb52ce-8fdc-22d0-06b9-e7f7fc2d222e@gmail.com>
On 08/22/2017 10:58 AM, Martin Sebor wrote:
> On 08/21/2017 07:41 PM, Daniel Santos wrote:
>> It took me a while to figure out how to do this so I figured that it
>> should be
>> in the docs. OK for trunk?
>>
>> * doc/install.texi: Add more details on selecting multiple tests.
>
> Thank you! It had taken me some time to figure this out.
>
>> +The file-matching expression following @var{filename}@command{.exp=}
>> is treated
>> +as a series of whitespace-delimited glob expressions so that
>> multiple patterns
>> +may be passed, although any whitespace must either be escaped or
>> surrounded by
>> +tick marks if multiple expressions are desired. For example,
>
> Do you mean single quotes?
Yes. I guess I've heard the terms "tick marks" and "single quotes" used
before. Perhaps using 'single quotes' would be a good way to express it
(with the quotes).
> I would suggest "escaped or quoted."
> The whole argument to RUNTESTFLAGS can be quoted in either single
> or double quotes and, AFAICT, so can the space-separated test
> names within it.
Well, mysteriously, double quotes do not work. So if I pass
RUNTESTFLAGS='"i386.exp=pr80969-[12]*.c pr80969-4.c"' then the second
pattern isn't used. I have NO idea what happens to it because it I pass
RUNTESTFLAGS='i386.exp=pr80969-[12]*.c pr80969-4.c' then runtest
properly demands that I tell it what in the hell pr80969-4.c is supposed
to mean. As an experiment, I created a symlink named \"pr80969-4.c and
using RUNTESTFLAGS='"i386.exp=pr80969-[12]*.c "pr80969-4.c' but it
didn't pick it up. This is probably JAB (just another bug) in DejaGNU.
Among the variations I've tried are enclosing the expressions in
{braces}, \{escaped braces\} and comma-delimited \{escaped,braces\},
but none of these worked.
Daniel
> Martin
>