testing consistency

Joel Sherrill joel@OARcorp.com
Fri Sep 5 07:26:00 GMT 1997


On Thu, 4 Sep 1997, Joe Buck wrote:

> This means that we should make sure to test the compilers that are built
> by following the (yet to be written) instructions exactly, that is,
> bootstrap the compiler and build with "-O2 -g", then doing tests with
> "clean" environments (nothing else installed: e.g. no libg++ if it isn't
> part of egcs).  Additional tests with higher optimization levels and
> extra headers are welcome but should be considered "extra".

I know I have built this way out of habit for years. :)

> Ideally, it should be extremely simple to run a "standard test" and
> do a full report of results, and mail it back to a standard address.
> e.g.
> 
> ./configure
> make
> make test_and_report
> 
> The idea is that this runs all the test suites, collects all of the
> relevant data, and sends it in a mail message.  It would be nice if
> cruft is deleted so the mail message isn't full of garbage.

This would also need to include a "compile but don't execute and report" 
for cross environments.  It would certainly save me a lot of setup effort.
:)

--joel




More information about the Gcc mailing list