This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [libgo] Improve Solaris 2/SPARC support


On Thu, 31 Mar 2011, Rainer Orth wrote:

> Ian Lance Taylor <iant@google.com> writes:
> 
> > Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE> writes:
> >
> >> I'm especially suffering from hangs on Solaris 8/x86 and Solaris 8 and
> >> 9/SPARC (not yet filed or investigated), which hangs the whole build (PR
> >> go/48242).  If I get around to it, I'll probably replace gotest by a
> >> dg-based testsuite.
> >
> > Argh, no, I am trying to fight against that as long as possible.  We
> > should be moving away from DejaGNU, not toward it.
> 
> Do you have a decent alternative?  I've no idea what happened to QMTest
> which CodeSourcery tried for the C++ testsuite.

QMTest works fine (and LSB uses it for running an old libstdc++ testsuite 
version, though there are lots of things weird about the LSB testsuites).  
<svn://source.codesourcery.com/qmtest/trunk> (and, for the qmtest_gcc code 
emulating an old version of GCC's test harness, 
<svn://source.codesourcery.com/qmtest_gcc/trunk>).  It has structured 
notions of tests, hosts, results, expectations etc., and doesn't hardwire 
loads of knowledge about the details of a GCC build tree.

> I'm certainly not enamored with Tcl, Expect and DejaGnu, but so far they
> do a decent job.  Having each library run its testsuite as it pleases
> with different output and different ways of dealing with XFAILs,
> target-dependent options and stuff, is completely unmaintainable IMO.

Indeed.  And the main thing required for converting to another harness 
would be rewriting the large piles of existing Tcl code that handles all 
the GCC-specific testsuite features (and, quite possibly, the code in 
dg.exp; the emulation would need to be sufficiently compatible) to work 
with the new harness's interfaces.  You need a clear way to convert all 
testsuites.  Note that the amounts of custom Tcl code have grown massively 
since the previous experiments with emulation in QMTest.

-- 
Joseph S. Myers
joseph@codesourcery.com


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]