Hi Tom,

>>>>>>> "Rainer" == Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE> writes:
>>
>> Rainer> Therefore I propose to update both files from the gcc repo.  The
>> Rainer> changes
>> Rainer> to the .sh version are trivial, just counting the number of DejaGnu
>> Rainer> ERROR lines, too.
>>
>> Thank you for doing this.  This is ok.
>>
>> Rainer> * One could keep the files in toplevel contrib as in gcc, instead of
>> Rainer>   stashing them away in gdb/testsuite.
>>
>> I don't have an opinion on this one, either way is ok by me.
>
> On second thought, there are some arguments for moving them to toplevel
> contrib:
>
> * This way, they can easily be used should someone decide to parallelize
>   one or more of the binutils, gas, or ld testsuites.
>
> * They are less easily overlooked for updates from the gcc repo when
>   they reside in the same place in both.
>
> * The test_summary script needs to live in contrib since the toplevel
>   Makefile's mail-report.log target expects it there.
>
> So I'll go that route.

here's what I'm going to check in shortly.  Tested on amd64-pc-solaris2.11 with

	make -j16 check
and
	make -j16 -k RACY_ITER=5 check

	Rainer

-- 
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University


2018-06-13  Rainer Orth  <ro@CeBiTec.Uni-Bielefeld.DE>

	gdb/testsuite:
	* dg-extract-results.sh: Move to toplevel contrib.
	* Makefile.in (check-parallel): Reflect dg-extract-results.sh move.
	* Makefile.in (check-parallel-racy): Likewise.

	contrib:
	* dg-extract-results.sh: Move from gdb/testsuite.
	Update from gcc repo.
	* dg-extract-results.py: New from gcc repo.