Re: C++ compatibility testing

[Phil Edwards <phil at jaj dot com>]

On Wed, Sep 25, 2002 at 10:51:35AM -0700, Janis Johnson wrote:
> On Sat, Sep 21, 2002 at 02:36:54PM -0400, Phil Edwards wrote:
> > 
> > I will be using the second approach, since I already have both compilers:
> > 
> >     http://gcc.gnu.org/ml/gcc/2002-08/msg01133.html
> > 
> > For each night, I can just run the autocrasher, then I have both branches
> > available in an easily computable pathname:
> > 
> >     27% ls -d build/*2002-09-21*
> >     build/build-2002-09-21/        build/install-2002-09-21/
> >     build/build-2002-09-21-3.2/    build/install-2002-09-21-3.2/
> >     build/build-2002-09-21-trunk/  build/install-2002-09-21-trunk/
> >     28%

I've got this working now, by simply setting the correct variables, and
then calling (an unmodified copy of) your script.


> I'd like to somehow specify the installation location of the second
> compiler to use, probably as an environment variable.  Keeping object
> files around is just too messy.

Very reasonable.


> I tried QMTest last May and had problems, probably because I was using
> Python 2.2 which doesn't seem to work with it.  Now I've got it working
> on i686-pc-linux-gnu and ia64-unknown-linux-gnu with:
> 
>   Python 2.1.3
>   QMTest 1.1.5
>   QMTC 1.2

I'm stuck:

    % make qmtest-g++
    echo "Determining expected results..."
    Determining expected results...
    cd qmtestsuite && qmtest  run  -C context \
               -c "GCCTest.generate_xfails=1" -o gpp-expected.qmr \
       gpp \
       > /dev/null
    qmtest: error: The extension class 'gcc_database.GCCDatabase' could not be
                   found.  You may need to set the 'QMTEST_CLASS_PATH' environment
                   variable.

    make: *** [qmtestsuite/gpp-expected.qmr] Error 1

I would set the variable if I knew what file it wanted.


> Using QMTest for the interoperability tests won't be practical unless
> GCC developers who want to run those tests are set up to use QMTest.
> Are they, and if not, will they be willing to set it up so they can run
> the new tests?

Probably not yet, and probably not yet, respectively.


Phil

-- 
I would therefore like to posit that computing's central challenge, viz. "How
not to make a mess of it," has /not/ been met.
                                                 - Edsger Dijkstra, 1930-2002