This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Lessons learned from compiler error/warnings tests
- From: Joseph Myers <joseph at codesourcery dot com>
- To: David Malcolm <dmalcolm at redhat dot com>
- Cc: Florian Weimer <fweimer at redhat dot com>, GCC <gcc at gcc dot gnu dot org>, GNU C Library <libc-alpha at sourceware dot org>
- Date: Fri, 9 Sep 2016 14:31:15 +0000
- Subject: Re: Lessons learned from compiler error/warnings tests
- Authentication-results: sourceware.org; auth=none
- References: <29835506-6a1a-d0f4-ff70-01e298928dd1@redhat.com> <1473430404.6782.9.camel@redhat.com>
On Fri, 9 Sep 2016, David Malcolm wrote:
> (FWIW, I'd much prefer it if DejaGnu were implemented in Python rather
> than Tcl; writing and debugging .exp files below gcc/testsuite is one
QMTest was a test harness written in Python and avoiding various issues
with DejaGnu's design, though by now it looks rather dated and I expect in
the modern Python world lots of things would be done differently. (Some
peculiarities of its design made it hard to fit in compiler tests that
test lots of things in the same compiler run, although there was an
emulation of running the GCC tests as they were at that time, and GDB
tests would have been particularly problematic.) I think both DejaGnu and
QMTest have useful lessons in how to design test harness software.
--
Joseph S. Myers
joseph@codesourcery.com