This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: How to see labels in common block
- To: Toon Moene <toon at moene dot indiv dot nluug dot nl>
- Subject: Re: How to see labels in common block
- From: Jeffrey A Law <law at cygnus dot com>
- Date: Tue, 15 Feb 2000 13:30:28 -0700
- cc: Andy Vaught <andy at maxwell dot la dot asu dot edu>, gcc-patches at gcc dot gnu dot org
- Reply-To: law at cygnus dot com
In message <38A9B600.C069E005@moene.indiv.nluug.nl>you write:
>
> > As far as improving the testsuite, we might consider simply downloading
> > a million lines of code from netlib. It isn't something that we can pack
> > up and distribute, but in those million lines, every silly thing that you
> > can do with fortran is done someplace.
>
> No, I don't like that. We should add testcases to the testsuite that
> really point to problems. Otherwise it'll get much to expensive to run
> testsuites. Furthermore - an observation I borrow from Mike Stump - a
> testcase is pointing at a weak spot in the compiler. We might get it
> wrong again.
I agree with Toon.
Our testsuite is a regression testsuite -- meaning it tests for bugs that
have already been reported to make sure we don't mess them up again. The
tests are meant to be small, which keeps the compile/run time reasonable
and makes the tests understandable, even to those not 100% familiar with
the test itself.
We have a separate process for doing larger scale testing as part of our
release process. For example, we used lapack as part of our testing
program for the gcc-2.95 release.
jeff