When looking at the gdb.sum file produced by dg-extract-results.sh on
Solaris 11/x86, I noticed some wrong sorting, like this:

PASS: gdb.ada/addr_arith.exp: print something'address + 0
PASS: gdb.ada/addr_arith.exp: print 0 + something'address
PASS: gdb.ada/addr_arith.exp: print something'address - 0
PASS: gdb.ada/addr_arith.exp: print 0 - something'address

Looking closer, I noticed that while dg-extract-results.sh had been
copied over from contrib in the gcc repo, the corresponding
dg-extract-results.py file had not.  The latter not only fixes the
sorting problem I'd observed, but is also way faster than the shell
version (like a factor of 50 faster).

Therefore I propose to update both files from the gcc repo.  The changes
to the .sh version are trivial, just counting the number of DejaGnu
ERROR lines, too.

There are other possible improvements in this area:

* One could keep the files in toplevel contrib as in gcc, instead of
  stashing them away in gdb/testsuite.

* One could also copy over gcc's contrib/test_summary, used by the
  toplevel make mail-report.log to provide a nice summary of test
  results.  However, this is currently hampered by the fact that for
  parallel make check the gdb.sum and gdb.log files are left in
  outputs/*/*/gdb.{sum,log} after dg-extract-results.sh has run instead
  of moving them to *.sep like gcc's gcc/Makefile.in does, so
  mail-report.log lists every failure twice.

Thoughts?

	Rainer

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


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

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