This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: V3: SPARC bug and tree freeze
- To: aj at suse dot de, mark at codesourcery dot com
- Subject: Re: V3: SPARC bug and tree freeze
- From: dewar at gnat dot com (Robert Dewar)
- Date: Sun, 12 Nov 2000 07:42:07 -0500 (EST)
- Cc: gcc-bugs at gcc dot gnu dot org, gcc at gcc dot gnu dot org
<<glibc is too big to use as a check-in criteria. However, it should be
part of the release testing process, and nightly jobs to test
substantial programs (like glibc) are a Good Thing.
>>
Is that really true with modern fast computers. In the GNAT world, the
checkin criterion for even the tiniest "can't-possibly-affect-anything"
modification is to run the entire internal regression suite (about 7000
test cases, about 7 million lines of code). The way we do it is with
a robot that accepts the patch as a message and runs the suite
automatically. It takes a few hours of running time on a fast machine.
Certainly testing glibc sounds like something that could be done quite
quickly.