Re: GCC 3.2

[Benjamin Kosnik <bkoz@redhat.com>]

> > > split tests to compile pieces with two compilers
> > >   http://gcc.gnu.org/ml/gcc/2002-08/msg00712.html
> > > 
> > >   covers:
> > >     anything for the compiler and runtime support library
> > > 
> > >   advantages:
> > >     has the potential to uncover unexpected problems that wouldn't be
> > >     detected by other testing
> > > 
> > >   disadvantages:
> > >     doesn't yet exist
> > > 
> > >     won't easily fit into the GCC testsuite
> > >       need to have two compilers available when tests are run or else
> > >       save baseline object files for each platform (.o, .so, .a)
> > > 
> > >       building static libraries and shared objects is OS-dependent
> > 
> > I might just have a go at this.  Right now I've automated the "test both
> > branches, swap the .so's, test both branches again" test that people tried
> > just before the 3.2 release.  So the two-compilers problem is solved.
> 
> This approach uses two compilers to build pieces of a single test which
> are then linked together and run.  Is that problem solved?

Phil seems to be working on it. I noticed you also posted a shell script
to do it. At some point this should be spelled out and put in the docs.

> > This document is extraordinarily helpful.  Thanks!
> 
> Then I'll keep updating it.  Would this be useful as part of the
> projects list while we figure out what needs to be done?

Yes. You can add it to libstdc++-v3/docs/html/abi.txt if you'd like.

Thanks!
benjamin