This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: Question On Testsuite 12/22/07
- From: Tim Prince <tprince at myrealbox dot com>
- To: Thomas Dineen <tdineen at ix dot netcom dot com>
- Cc: Alex Man <alexman at seas dot ucla dot edu>, Dennis Clarke <dclarke at blastwave dot org>, GCC Help <gcc-help at gcc dot gnu dot org>
- Date: Wed, 26 Dec 2007 09:29:57 -0800
- Subject: Re: Question On Testsuite 12/22/07
- References: <200712212217.OAA06291@whittier.seas.ucla.edu> <476D8222.8080901@ix.netcom.com>
Thomas Dineen wrote:
> Snipped from the bottom of this post:
> "or the test suite results are shoddy or something."
>
> When we build gcc is it really necessary to run the test suite?
> When we run the test suite are we testing for build bugs or
> some type of traditional source code bugs?
>
> Are their build bugs which are not reported as obvious errors?
>
I would want to verify that my build works as expected, by comparing
with results reported by others. Also, when I am building for an
infrequently reported target, I post results in the hope that someone
will make use of them, either for fixes, to verify their own builds, or
to inform me of improvements.
Lately, I have chosen not to incorporate known fixes (mostly for
testsuite bugs on secondary targets) which aren't accepted into
mainline, assuming that others will build the same way, should they
choose to compare.