brooks@maddog.llnl.gov (06/19/89)
Several posters have indicated, and later strongly supported, statements about reliability problems with GCC. As you might guess at this point, the reliability problems are real. The reason why new releases are often flakey is probably the lack of sufficient regression testing. A regression test package should be built and distributed as part of GCC. Before each publicly announced release FSF should ship the new release to several friendly sites which will run the regression tests on hardware FSF does not have direct access to. The major problem with regression test packages is the sheer volume of code which must be written, with the writer thinking that he is not doing something useful (like working directly on the compiler). The solution to this problem is to request that bug reports include if possible a test program which is in the standard regression test format. Suitable requirements: A single program which runs and produces the message PASSED or FAILED on standard output. The regression test driver can trigger on these keywords and inform the tester. Liberal use of tests for failure with suitable printing of line and file numbers of where the compilation failure occured. A pointer to the source of the test program in case help is required in bug shooting the compiler. With all the bug reports which are coming in, it should be no time at all that we have a large and useful regression test library for GCC. At least we wont have repeat visits on previous bugs. brooks@maddog.llnl.gov, brooks@maddog.uucp
msnyder@sioux.cis.ohio-state.edu (Michael V Snyder) (06/21/89)
In regard to establishing a regression test suite for the compiler, I think this is a very good idea! Sorry, I can't flat out do it, but since I'm now working on a port, I could take part in the effort. After all, I have to test my port! Michael Snyder msnyder@csi.compuserve.com msnyder@cis.ohio-state.edu